Usage of the Me Parameter in the Access Token Response
- Dominant language
- HTML
- Stars
- 57
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
This is the result of a conversation @gRegorLove and I had at IWC SD 2023 today.
In my implementation, I take the me property of the access token response and use this as the user identifier.
@gRegorLove pointed out this idea is not explicit in the specification. It is implied by the fact that the 'me' entered into the client need not be the same URL output as the 'me' parameter, however, which was my assumption.
Proposing that this be noted more explicitly in the specification.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no specification file or test. Locate the IndieAuth specification entry point, review the access-token response section and the existing discussion, then clarify that the returned `me` identifies the user; done when the specification explicitly states this behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100