--- title: OpenID Connect 1.0 & OAuth 2.0 --- ### Endpoints and Domains This chapter documents the [OpenID Connect 1.0](https://openid.net/connect/) and [OAuth 2.0](https://oauth.net/2/) features provided by **ZITADEL**. Under normal circumstances **ZITADEL** need four domain names to operate properly. | Domain Name | Example | Description | |:------------|:--------------------|--------------------------------------------------------------------------------------------------------------------------------------| | issuer | issuer.zitadel.ch | Provides the [OpenID Connect 1.0 Discovery Endpoint](#openid-connect-10-discovery) | | api | api.zitadel.ch | All ZITADEL API's are located under this domain see [API explanation](develop#APIs) for details | | login | accounts.zitadel.ch | The accounts.* page provides server renderer pages like login and register and as well the authorization_endpoint for OpenID Connect | | console | console.zitadel.ch | With the console.* domain we serve the assets for the management gui | #### OpenID Connect 1.0 Discovery The OpenID Connect Discovery Endpoint is located within the issuer domain. For example with [zitadel.ch](zitadel.ch) this would be the domain [issuer.zitadel.ch](issuer.zitadel.ch). This would give us [https://issuer.zitadel.ch/.well-known/openid-configuration](https://issuer.zitadel.ch/.well-known/openid-configuration). **Link to spec.** [OpenID Connect Discovery 1.0 incorporating errata set 1](https://openid.net/specs/openid-connect-discovery-1_0.html) #### authorization_endpoint [https://accounts.zitadel.ch/oauth/v2/authorize](https://accounts.zitadel.ch/oauth/v2/authorize) > The authorization_endpoint is located with the login page, due to the need of accessing the same cookie domain #### token_endpoint [https://api.zitadel.ch/oauth/v2/token](https://api.zitadel.ch/oauth/v2/token) #### userinfo_endpoint [https://api.zitadel.ch/oauth/v2/userinfo](https://api.zitadel.ch/oauth/v2/userinfo) #### end_session_endpoint [https://accounts.zitadel.ch/oauth/v2/endsession](https://accounts.zitadel.ch/oauth/v2/endsession) > The end_session_endpoint is located with the login page, due to the need of accessing the same cookie domain #### jwks_uri [https://api.zitadel.ch/oauth/v2/keys](https://api.zitadel.ch/oauth/v2/keys) > Be aware that these keys can be rotated without any prior notice. We will however make sure that a proper `kid` is set with each key! #### OAuth 2.0 Metadata **ZITADEL** does not provide a OAuth 2.0 Metadata endpoint but instead provides a [OpenID Connect Discovery Endpoint](#openid-connect-10-discovery). ### Scopes #### How scopes work > TODO describe #### Reserved Scopes In addition to the standard compliant scopes we utilize the following scopes. | Scope | Description | Example | |:------------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| | urn:zitadel:iam:org:project:role:{rolename} | By using this scope a [client](administrate#clients) can request the claim urn:zitadel:iam:roles:rolename} to be asserted when possible. As an alternative approach you can enable all [roles](administrate#Roles) to be asserted from the [project](administrate#projects) a [client](administrate#clients) belongs to. See details [here](administrate#RBAC_Settings) | urn:zitadel:iam:org:project:role:user | | urn:zitadel:iam:org:domain:primary:{domainname} | When requesting this scope **ZITADEL** will enforce that the user is a member of the selected organisation. If the organisation does not exist a failure is displayed | urn:zitadel:iam:org:domain:primary:acme.ch | | urn:zitadel:iam:role:{rolename} | | | ### Claims > TODO describe #### Reserved Claims | Claims | Description | Example | |:------------------------------------------------|:------------|----------------------------------------------------------------------------------| | urn:zitadel:iam:org:domain:primary:{domainname} | | `{"urn:zitadel:iam:org:domain:primary": "acme.ch"}` | | urn:zitadel:iam:org:project:roles:{rolename} | | `{"urn:zitadel:iam:org:project:roles": [ {"user": {"id1": "acme.zitade.ch", "id2": "caos.ch"} } ] }` | | urn:zitadel:iam:roles:{rolename} | | | ### Grant Types For a list of supported or unsupported `Grant Types` please have a look at the table below. | Grant Type | Supported | |:------------------------------------------------------|:--------------------| | Authorization Code | yes | | Authorization Code with PKCE | yes | | Implicit | yes | | Resource Owner Password Credentials | no | | Client Credentials | yes | | Device Authorization | under consideration | | Refresh Token | work in progress | | JSON Web Token (JWT) Profile | partially | | Security Assertion Markup Language (SAML) 2.0 Profile | no | | Token Exchange | work in progress | #### Authorization Code **Link to spec.** [The OAuth 2.0 Authorization Framework Section 1.3.1](https://tools.ietf.org/html/rfc6749#section-1.3.1) #### Proof Key for Code Exchange **Link to spec.** [Proof Key for Code Exchange by OAuth Public Clients](https://tools.ietf.org/html/rfc7636) #### Implicit **Link to spec.** [The OAuth 2.0 Authorization Framework Section 1.3.2](https://tools.ietf.org/html/rfc6749#section-1.3.2) #### Client Credentials **Link to spec.** [The OAuth 2.0 Authorization Framework Section 1.3.4](https://tools.ietf.org/html/rfc6749#section-1.3.4) #### Refresh Token **Link to spec.** [The OAuth 2.0 Authorization Framework Section 1.5](https://tools.ietf.org/html/rfc6749#section-1.5) #### JSON Web Token (JWT) Profile **Link to spec.** [JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants](https://tools.ietf.org/html/rfc7523) #### Token Exchange **Link to spec.** [OAuth 2.0 Token Exchange](https://tools.ietf.org/html/rfc8693) ### Device Authorization **Link to spec.** [OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628) ### Not Supported Grant Types #### Resource Owner Password Credentials > Due to growing security concerns we do not support this grant type. With OAuth 2.1 it looks like this grant will be removed. **Link to spec.** [OThe OAuth 2.0 Authorization Framework Section 1.3.3](https://tools.ietf.org/html/rfc6749#section-1.3.3) #### Security Assertion Markup Language (SAML) 2.0 Profile **Link to spec.** [Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants](https://tools.ietf.org/html/rfc7522)