See: http://microformats.org/wiki/relmeauth for more details.
- 1 IndieWeb Examples
- 2 Testimonials
- 3 Implementations
- 4 FAQ
- 5 Issues
- 6 Articles
- 7 Brainstorming
- 8 See Also
http://microformats.org/wiki/RelMeAuth is nifty... like OpenId but even simpler.
RelMeAuth looks good, might have to re-add rel=me's to my site http://microformats.org/wiki/RelMeAuth
Invited to @IndieWebCamp, didn't have IndieAuth domain to login. Took 10s to add rel="me" to homepage. No "providers". Your move OpenID
Open source implementations
- IndieAuth.com - service and open source
- PHP: https://github.com/themattharris/RelMeAuth/
Q: Why does RelMeAuth need a silo backlink?
There are also usability, error detection, and recovery reasons for keeping such a double opt-in mechanism when delegating authentication. For example, it prevents one from delegating their RelMeAuth to another person's silo account.
Selectively Displaying rel-me Info
Selectively Displaying rel-me Info (e.g. hiding a one-off email address).
Ideally your site would know that the request was coming from an (your?) IndieAuth server, and only render your one-off email address if so.
This would require either
- some sort of pre-registration with the indieauth server so your site could verify a shared secret
- crypto signing with public keys so that pre-registration is not required
Here is a potential example flow.
- Sign in once to your IndieAuth server
- Click a "generate shared secret" button, which is some 128-bit string that the IndieAuth server stores internally on your user record.
- You take the string and add some code like this to your home page:
if header['IndieAuth-Secret'] == shared_secretwhich checks to see if the secret is passed in an HTTP header called "IndieAuth-Secret".
echo '<link rel="me" href="mailto:email@example.com">'
2 public key
- The IndieAuth server publishes its public key in its own h-card like
- When the IndieAuth server makes a request to fetch the HTML of your home page, it also adds an HTTP header which is a signature of the IndieAuth server hostname, your domain name and the timestamp. It would send three additional headers:
IndieAuth-signature: signature of indieauth.com;example.com;1378052578(Format is a placeholder, in reality we might use something closer to the JSON web token format or something)
- When your server gets the request for your home page, it can read the IndieAuth-server header to discover which server is making the request, then go fetch its public key.
- It would then compute the signature of the three pieces of information and verify that the signature passed in the header matches, at which point it can render the private info.
Please document here if there is some other existing mechanism that can solve this!
A potential workaround is putting your one-off email in a
<link> tag in your HTML head so that it isn't visible to viewers of your web page. While this doesn't actually prevent a person from seeing your one-off email, it is at least an unlikely place for them to look. Though robots would likely still index it, so this is not a sufficient workaround.
RDFa Parsing Problems
Consolidated identities do not carry inherent trust
- Identity consolidation, enabling things like distributed verification.
- Authentication through the linked identity.
These can sometimes be at odds with each other if the user does not trust the external profile page host to handle authentication. This can be because of lax security practices, a lack of certain features like 2FA, or any other subjective reason.
Martijn van der Ven has removed all
rel="me" attributes, as of 2018-02-15, from links to websites that do not support 2FA. He only wants to use authentication providers that offer 2FA as fallbacks to his IndieAuth endpoint. Even if that meant giving up on identity consolidation.
Possible solutions have been mentioned through an extra link relation:
- Dan Q wrote a GitHub issue against IndieAuth.com proposing a
non-authoritativelink relation that could be added next to
meto instruct a RelMeAuth implementation to not use that page for authentication.
- Josh Juran proposed a
authlink relation in reaction to Martijn’s comment. If an
authis detected on the page, all
merelations should be ignored for authentication.
- this seems nicer, explicitly calling out the trusted ones, and slightly nicer to implement. Also kind of establishes a pattern of rels to check in order: authorization_endpoint, auth, me sknebel
- agreed, it's kind of like the addition of the
authrel value on a link upgrades that page to be more secure. Aaron Parecki
- I can understand the desires to 1. provide a non-authorative broader identity consolidation (which you would do with rel=me as documented), 2. keep the simple rel=me way to do both consolidation and authn, 3. and a way to limit which of those you wanted used for authentication. In which case, I'd suggest "authn" as the new rel value to use. And then there are a number of possibilities for how it should work. I like the "upgrade a rel=me" semantic that Aaron Parecki suggests. Though the effect is more of a slight downgrade of all the *other* rel=me links on the page. - Tantek Çelik
- I don’t think it is either “upgrade” or “downgrade” at all. More of a branch off. For people with long lists of identities (I am approaching 30) trust may become an issue and thus branching authentication away from consolidation makes sense. Curious though: why the extra n in
authnfor the link relation? — Martijn van der Ven
- That seems more-elegant than my suggestion; presumably we'd want both attributes (i.e.
rel="me auth") in cases where the resulting link both represented me and could be used to authenticate me? So the process for an authenticator would be: (a) check for "auth", failing that (b) check for "me", and the process for a different service simply spidering for where I am found on the web found be: (a) just check for "me". Dan Q
- 2013-08-31 : On the Indie Web Camp Sign In UX Barrier (archived)
- 2013-08-31 : On evolving IndieAuth. (archived)
- 2013-12-08 : How to set up Web Sign In on your @squarespace website (archived)
Alternative flow for RelMeAuth via email
- ask the user for their email address (like Slack and nearly every other service)
- fetch the web page at the domain of their email address (e.g. firstname.lastname@example.org -> fetch https://aaronpk.com)
- look for rel=me links on that page
- if there is a rel=me link to their email address, use their domain name as their RelMeAuth identity
- send a one-time link to their email address
- when clicked, sign them in as their domain
note: obviously have a blacklist of bigco email providers domains that no one owns as a personal domain (gmail.com, hotmail.com, etc.)