Skip to content

Well Known Support #1607

@mod-flux

Description

@mod-flux

Summary of proposed feature
For OAuth providers that have .well-known configuration endpoints, offer the ability to provide these and have NextAuth dynamically discover and setup against all endpoints and everything that's provided as opposed to hardcoding all the endpoints manually.

Purpose of proposed feature
Dynamic service discovery is always advisable as it means the vendor can change their endpoints and/or configuration and a NextAuth enabled website can pick up the configuration dynamically and continue operating. Furthermore, it takes a lot of work out of manually configuring all of the endpoints which have inherent human error.

Detail about proposed feature
In the provider's options, provide the ability to set a .well-known endpoint and have the NextAuth service set up as per the configuration. Perhaps saving this configuration in the Lambda cache so it doesn't have to be requested every time.

Potential problems
Could conflict with other OAuth provider options. Could also lead to more time on the initial request.

Describe any alternatives you've considered
Manual configuration, which is what I've done to date.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions