-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support for GSuite SSO Groups membership #2455
Comments
Fixes #2455 This commit adds support for fetching groups for GSuite SSO logins via OIDC connector interface. If OIDC connector has a special scope: `https://www.googleapis.com/auth/admin.directory.group.readonly` teleport will fetch user's group membership and populate groups claim.
@klizhentas the |
nevermind |
Fixes #2455 This commit adds support for fetching groups for GSuite SSO logins via OIDC connector interface. If OIDC connector has a special scope: `https://www.googleapis.com/auth/admin.directory.group.readonly` teleport will fetch user's group membership and populate groups claim.
Fixes #2455 This commit adds support for fetching groups for GSuite SSO logins via OIDC connector interface. If OIDC connector has a special scope: `https://www.googleapis.com/auth/admin.directory.group.readonly` teleport will fetch user's group membership and populate groups claim.
converted this to doc ticket |
Fixes #2455 This commit adds support for fetching groups for GSuite SSO logins via OIDC connector interface. If OIDC connector has a special scope: `https://www.googleapis.com/auth/admin.directory.group.readonly` teleport will fetch user's group membership and populate groups claim.
@klizhentas Do all Teleport users within the given Google organization need to have permissions on |
@klizhentas see above. I will need this for the docs too. |
Closing issue as added in #2787 |
Description
Currently GSuite SSO is supported via standard OIDC SSO flow, but groups membership is not exposed via claims. Fix this by adding support.
No special resource type is required, here is how OIDC resource with extra claims
looks like:
IMPORTANT: the groups will be fetched only if admins include special auth scope
https://www.googleapis.com/auth/admin.directory.group.readonly
in the scopes of the connector as shown in the example above.Additional setup steps
Set up OIDC client as described here
Redirect URL Domain has to be verified in the list of verified domains in the project API page.
Admin Directory API has to be turned on. Enable it by visiting https://console.developers.google.com/apis/api/admin.googleapis.com/overview then retry.
The text was updated successfully, but these errors were encountered: