feat: assign users to teams via OIDC claims #1393
|
@ -14,9 +14,9 @@ Teams which exist only because they were created from oidc attributes are not ed
|
|||
|
||||
To distinguish between teams created in Vikunja and teams generated automatically via oidc, generated teams have an `oidcID` assigned internally.
|
||||
|
||||
You need to make sure the OpenID provider has the `vikunja_groups` scope via your custom scope since this is the key, which is looked up by Vikunja to start the procedure.
|
||||
You need to make sure the OpenID provider offers a `vikunja_groups` key through your custom scope. This is the key, which is looked up by Vikunja to start the procedure.
|
||||
|
||||
Additionally, make sure to deliver an `oidcID` and a `name` attribute in the oidc token.
|
||||
Additionally, make sure to deliver an `oidcID` and a `name` attribute within the `vikunja_groups`. You can see how to set this up, if you continue reading.
|
||||
|
||||
### Setup in Authentik
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user
Here it is called
vikunja_groups
and in the text before it'svikunja_scope
. Should this be the same?one is the required scope, which has to be customized -> vikunja_scope
another one is a key for the groups within this scope -> vikunja_groups.
the scope attribute in vikunja should be pluralized into "scopes"
in authentik the attribute that is asked for is referred to as scope.
Can you add this explanation to the docs?
I changed the docs a little to clarify this.
5f521c0982
Not sure if there is more needed.