Skip to content

Decouple clients and OAuth2 Flow types #387

Description

@krotscheck

At this point, creating a client requires that we explicitly set the OAuth2 flow which this client adheres to. This prevents a client from using multiple authentication methods, such as "Facebook, Google, Linkedin via Implicit, Password via Owner Credentials".

It'd be nice if a single client ID can be used both for initiating an implicit/auth code flow via an IdP, or via password.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions