feat: add Asgardeo authentication provider#1889
Open
srinidhipappu wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds an official Asgardeo authentication provider to
@nuxtjs/auth. The new provider uses the existing OpenID Connect scheme and automatically derives the Asgardeo OIDC discovery endpoint from the configured issuer, allowing Nuxt developers to integrate Asgardeo authentication with minimal configuration instead of manually setting OIDC endpoints.Why was this PR needed?
This PR addresses issue #364. Currently, Asgardeo users must configure a generic OpenID Connect strategy manually, including discovery endpoints, token handling, and authentication settings. Investigation showed that the existing OpenID Connect scheme already supports the required authentication flow, including authorization code flow, PKCE, token handling, user information retrieval, and logout through discovery.
This implementation adds a dedicated provider that follows the same architecture as existing providers, such as Auth0, while reusing the existing OpenID Connect functionality. Developers only need to provide the Asgardeo
clientIdandissuer, and the provider handles the remaining configuration automatically.What are the relevant issue numbers?
Closes #364
Does this PR meet the acceptance criteria?