Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should a token grant access to anything more specific than the specified resource? #83

Open
aaronpk opened this issue Jul 8, 2021 · 1 comment
Labels
ticketing extension Ticketing for IndieAuth extension

Comments

@aaronpk
Copy link
Member

aaronpk commented Jul 8, 2021

(copying from the wiki)

Would a token grant access to anything more specific than the provided resource, or would it be only for that specific resource? (e.g. should a token for https://example.com/alice/ also work on https://example.com/alice/feed)

  • Giving meaning to the URLs like this is convenient but may be misleading or break security boundaries in unexpected ways.
  • An alternative would be to include another parameter, such as the previously discussed "realm", or somehow using scopes for this.
  • Following RFC8707: Resource Indicators for OAuth 2.0 this would mean allowing resource=https://example.com/alice/ to be used to retrieve the value of https://example.com/alice/feed
    • This allows the use of multiple resource parameters for the purpose of multiple resource URLs to provide access to
@aaronpk aaronpk added the ticketing extension Ticketing for IndieAuth extension label Jul 8, 2021
@dshanske
Copy link
Member

dshanske commented Jul 8, 2021

Related #82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ticketing extension Ticketing for IndieAuth extension
Development

No branches or pull requests

2 participants