Skip to content

feat: OIDC claims #928

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

Merged
merged 1 commit into from
Mar 30, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions admin/access-control/manage.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,20 @@ If you opt for **OpenID Connect**, you'll need to provide additional
configuration steps, which are detailed in the subsequent sections of this
article.

## Requirements

Coder expects the following [OIDC claims](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1#whats-a-claim)
from your OIDC provider:

- `email`

- `name` (full name/display name)

Comment on lines +23 to +25
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `name` (full name/display name)
- `name` (full name/display name)

- `preferred_username` (username for dev URLs)
Comment on lines +24 to +26
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not required, we will derive the username from the first part of the email address before the @ and we will derive the name from the username.


You may need to map these to your existing claims within your OIDC provider's
admin console.

## Set up OIDC authentication

To set up OIDC authentication, you'll first need to register a Coder application
Expand Down