Skip to content

Should the client_name be a unique field? #7

@reginafcompton

Description

@reginafcompton

The OAuth2ClientMixin provides a client_name field, but does not mark it as unique.
https://github.com/lepture/authlib/blob/18858b7e84b33dd5dd20b64a664287ba17e0ccd4/authlib/flask/oauth2/sqla.py#L32

I can imagine a Facet user creating clients with the same client name, which could cause confusion, as a DT grows. Should we override the client_name (from OAuth2ClientMixin) in the Authserver modal and mark it as unique?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions