-
Notifications
You must be signed in to change notification settings - Fork 9
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
Auth documentation and Issuer claim #373
Conversation
including using docker to install composer deps
add OpenID Connect (OIDC) and OAuth 2.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I've changed a few things in the README files, including merging some of @tristan-orourke and @JoshBeveridge documentation for the root README.
README.md
Outdated
- [PHP 7.4](https://www.php.net/downloads) | ||
- [Composer](https://getcomposer.org/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically you can actually avoid installing these by using Docker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, this ties in a bit to the discussion about Docker-only instructions or not.
Resolves #280.
I was originally trying to configure Laravel Passport to be more in line with OpenIDConnect (instead of only Oauth2). Things like the id token + access token, and an introspection endpoint. However, I realized over time that it would a lot of work (I couldn't find a good package that did what I wanted, including working with Laravel Passport) and isn't really required for our current use case.
For now, I added more documentation which should be helpful to anyone else on the team working on Authentication.
I also was able to override the generation of access tokens. (This thread and this code were my main references.) For now the only difference with my custom access token is that it includes the Issuer claim (iss), an extremely common component to OAuth tokens (and required for OIDC).