Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable scopes/claims for SSO providers #468

Open
verymilan opened this issue Feb 11, 2024 · 1 comment
Open

Configurable scopes/claims for SSO providers #468

verymilan opened this issue Feb 11, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@verymilan
Copy link

Hi there, I have connected a Zitadel to Linkwarden – however that connector itself did not work (as the docs warn). I then chose the Keycloak connector which works fine but lacks the proper scope for the username (and more, see below). This wouldn't be so bad if the application wasn't blocking

  • Displayname
  • Username
  • Avatar (which is usually not set by users in the sso provider)
  • ...?

Sadly it does not look like i can adjust the scopes without patching the code for my needs, because there is no generic provider or global option to aditionally set.

Right now my User table looks like:

 id | name | username | email | emailVerified | password | isPrivate |        createdAt        | archiveAsPDF | archiveAsScreenshot | archiveAsWaybackMachine | image |        updatedAt
----+------+----------+-------+---------------+----------+-----------+-------------------------+--------------+---------------------+-------------------------+-------+-------------------------
  1 |      |          |       |               |          | f         | 2024-01-30 17:42:16.232 | t            | t                   | f                       |       | 2024-01-30 17:42:16.232
@verymilan verymilan added the enhancement New feature or request label Feb 11, 2024
@samip5
Copy link

samip5 commented Feb 18, 2024

You can also potentially use actions in Zitadel to expose the things that would be exposed normally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants