towk/opaal
1
0
Fork 0
mirror of https://github.com/davidallendj/opaal.git synced 2025-12-20 03:27:02 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Changed the meaning of OPAAL in README.md

Browse source
This commit is contained in:
David J. Allen 2024-03-21 08:51:15 -06:00
parent 5173701fa0
commit 745fc5910a
No known key found for this signature in database
GPG key ID: 717C593FF60A2ACC
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -1,4 +1,4 @@
# OIDC Provider Authentication/Authorization Login (OPAAL) # OIDC Provider Automated Authorization Login (OPAAL)
This is a small, simple, experimental OIDC login helper tool that automates the authorization flows defined by [RFC 6749](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1) for social sign-in with identity providers (IdP) like Google, Facebook, or GitHub. This tool is made to work when your identity provider is separate from your authorization server, and we only need the IdP to receive an ID token. In this document, the identity provider (or authentication server) is strictly the OIDC implementation that identifies the resource owner (ID token) whereas the resource provider (or authorization server) is the OIDC implementation that grants access to a resource (access token). OPAAL assumes that the authentication server is external and the authorization server is owned. This tool is tested with Ory Kratos and Hydra for user identity and session management and OAuth2/OIDC implementation respectively. This is a small, simple, experimental OIDC login helper tool that automates the authorization flows defined by [RFC 6749](https://datatracker.ietf.org/doc/html/rfc6749#section-4.1) for social sign-in with identity providers (IdP) like Google, Facebook, or GitHub. This tool is made to work when your identity provider is separate from your authorization server, and we only need the IdP to receive an ID token. In this document, the identity provider (or authentication server) is strictly the OIDC implementation that identifies the resource owner (ID token) whereas the resource provider (or authorization server) is the OIDC implementation that grants access to a resource (access token). OPAAL assumes that the authentication server is external and the authorization server is owned. This tool is tested with Ory Kratos and Hydra for user identity and session management and OAuth2/OIDC implementation respectively.
@ -121,4 +121,4 @@ options:
- Fix how OAuth clients are managed with the authorization server - Fix how OAuth clients are managed with the authorization server
- Fix how the trusted issuer is added to the authorization server - Fix how the trusted issuer is added to the authorization server
- Allow signing JWTs by supplying key pair - Allow signing JWTs by supplying key pair
- Separate `jwt_bearer` grant type from the authorization code flow - Separate `jwt_bearer` grant type from the authorization code flow