Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Okta OIDC & Bitwarden - use Okta org auth server instead of custom auth server #835

Open
TomTomNavigator opened this issue Dec 17, 2021 · 0 comments

Comments

@TomTomNavigator
Copy link

TomTomNavigator commented Dec 17, 2021

Hi all,

according to https://bitwarden.com/help/article/oidc-okta/ you should use a custom auth server in Okta (default is the first custom auth server, a bit confusing - I know)

The thing is: not all subscriptions have custom auth servers!

I did not try, but what I read: Bitwarden does NOT need any custom claims or scopes - then you would be good to just use the Okta org auth server, which is always included (in any subscription).

You can browse to the discovery endpoint with your browser to get the proper values for your Okta org, as described here:
https://developer.okta.com/docs/concepts/auth-servers/#org-authorization-server-discovery-endpoints

OpenID: https://${yourOktaOrg}/.well-known/openid-configuration
OAuth: https://${yourOktaOrg}/.well-known/oauth-authorization-server
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant