Support RelMeAuth
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
A lot of folks (and IndieWeb guidance) still refer to RelMeAuth. This could be supported in Authl, although it might not be particularly straightforward. Idea for the flow:
- RelMeAuth provider has access to the Authl container
- For each
rel="me"link on the identity page, see if Authl supports it, and if so, use that - Proxy the identity flow for the returned identity link
- Return the original URL as the profile page. Bonus: Fuse the identity provider's profile with the h-card profile?
OPTIONAL: It would be nice if Handler.handles_page is able to provide an extended name, e.g. "RelMeAuth (via Twitter)". Since handles_page currently returns bool it could be changed to return Union[bool,str] and if it's a str that's a signal that it overrides the name.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the proposed RelMeAuth flow and inspecting the existing Handler.handles_page behavior. Determine how supported rel="me" links could select an Authl provider and proxy the returned identity. Done means the original URL is returned as the profile page, with the optional extended provider name considered separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100