How do I set up OpenID Connect (OIDC) Single Sign-On for My20i?
My20i supports OpenID Connect (OIDC) Single Sign-On (SSO), allowing you and your team members to log in using an existing identity provider rather than managing separate login credentials.
This allows you to use an identity provider such as JumpCloud, Keycloak or PocketID to authenticate users accessing your My20i account.
Before you begin
To configure OpenID Connect SSO, you'll need:
- Administrator access to your identity provider.
- Access to the My20i account owner's login and current password.
- Users configured within your identity provider, with email addresses matching their My20i usernames.
- Permission to create and configure OIDC applications within your identity provider.
Step 1: Create an OIDC application in JumpCloud
First, you'll need to register My20i as an application within JumpCloud.
- Log in to your JumpCloud administrator console.
- Navigate to SSO Applications.
- Select Add New Application.
- Choose Custom OIDC App.
- Open the SSO tab to configure the application.
Configure the following settings:
| Setting | Value |
|---|---|
| Grant Type | Authorisation Code only |
| Refresh Token | Disabled |
| Redirect URIs | https://my.20i.com/login/openid |
| Client Authentication Type | Client Secret Basic |
| Login URL | https://my.20i.com/login-sso |
| Subject Claim | JumpCloud User ID (Recommended Default) |
| Standard Scopes | Email and Profile |
| User Consent | Automatically consent |
You can leave the User Attributes, Constant Attributes and Include Group Attribute settings empty, as these are not required.
Note: The Redirect URL must match exactly, without a trailing slash. My20i also requires a confidential client that uses a client secret, so do not select Public (None PKCE) as the authentication type.
Once configured:
- Save your application.
- JumpCloud will display a Client ID and Client Secret. Make a note of these and store them securely, as the Client Secret is only displayed once.
- Navigate to the application's User Groups tab.
- Select the groups containing users who should be permitted to access My20i.
- Save your changes.
Only users assigned to the application through the selected groups will be able to authenticate using JumpCloud.
Step 2: Find your JumpCloud Issuer URL
Before configuring SSO in My20i, you'll need the correct Issuer URL for your JumpCloud account.
JumpCloud operates separate US and EU environments, so the correct URL depends on which region your organisation uses.
| JumpCloud region | Console address | Issuer URL |
|---|---|---|
| US | console.jumpcloud.com | https://oauth.id.jumpcloud.com/ |
| EU | console.eu.jumpcloud.com | https://oauth.id.eu.jumpcloud.com/ |
Check the address you use to access the JumpCloud administrator console and select the corresponding Issuer URL.
Note: Using the wrong regional Issuer URL may allow the configuration to save in My20i, but authentication will fail because JumpCloud cannot locate your application.
Step 3: Enable OpenID Connect SSO in My20i
Once your application has been configured in JumpCloud, you'll need to connect it to My20i.
- Log in to My20i as the account owner.
- Navigate to Account > Security Details.
- Locate the Single Sign-On section.
- Select OpenID Connect as your SSO provider.
- Enter the following information:
| Field | Value |
|---|---|
| Issuer URL | Your JumpCloud Issuer URL from Step 2 |
| Client ID | The Client ID provided by JumpCloud |
| Client Secret | The Client Secret provided by JumpCloud |
| Current Password | Your current My20i account owner password |
6. Save your configuration.
My20i will automatically retrieve and validate your identity provider's OpenID Connect configuration.
If the configuration cannot be validated, an error will be displayed explaining the issue.
Once saved, your OpenID Connect provider will be configured for My20i authentication.
Note: Existing SSO settings cannot be edited directly. If you need to change the Issuer URL, Client ID or Client Secret, you'll need to delete the existing SSO configuration and add it again.
Step 4: Test your SSO login
We recommend testing your configuration in a private or incognito browser window before relying on SSO for account access.
To test the login:
- Open https://my.20i.com/login-sso. Alternatively, select Go to SSO gateway from the standard My20i login page.
- Enter your My20i email address.
- Select Continue to SSO gateway.
- You'll be redirected to JumpCloud to authenticate.
- Enter your JumpCloud credentials and complete any additional authentication requirements configured by your organisation.
- Once authenticated, you'll be redirected back to My20i and logged in.
If successful, your OpenID Connect SSO configuration is working.
We recommend retaining access to your existing My20i password login until you've confirmed SSO is working correctly.
Can I log in directly from JumpCloud?
Yes. If the My20i application is available in your JumpCloud user portal, selecting it will direct you to the My20i SSO gateway.
You'll then enter your My20i email address to begin authentication.
All OpenID Connect login attempts start through the My20i SSO gateway, even when launching the application from JumpCloud.
How are My20i users linked to their SSO accounts?
When a user successfully authenticates through OpenID Connect for the first time, My20i associates their identity provider account with their existing My20i user.
For the initial login, the email address returned by the identity provider must match the My20i username being used to log in.
Once the initial authentication succeeds, My20i creates a link using the identity provider's Issuer and Subject identifiers.
This means:
- First login: The identity provider's email address must match the My20i username.
- Subsequent logins: My20i recognises the linked identity, even if the user's email address subsequently changes at the identity provider.
- One identity per user: Each My20i user can only be associated with one identity provider account. A different identity with the same email address cannot take over the existing link.
- Disabled users: My20i users who have been disabled cannot log in using SSO.
Note: Do not change the Subject Claim
Once users have successfully authenticated, you should not change the Subject Claim configured within your identity provider.
For example, changing the JumpCloud Subject Claim from JumpCloud User ID to Email will cause JumpCloud to return a different identity for your users.
As My20i still associates those users with their original identities, subsequent SSO login attempts will be refused.
If you've already changed this setting, restore the original Subject Claim. If you're unable to restore access, please contact 20i Support for assistance.
Using a different OpenID Connect provider
Although this guide uses JumpCloud, My20i also supports other standards-compliant OpenID Connect providers, including Keycloak and PocketID.
When configuring a different provider, you'll need to ensure it supports:
- Authorisation Code authentication using a confidential client and client secret.
- PKCE using S256.
- The
openid,emailandprofilescopes. - ID tokens signed using an asymmetric signing algorithm, such as RS256.
- A publicly accessible HTTPS Issuer URL with a valid OpenID Connect discovery document.
The Issuer URL is the base address associated with your provider's /.well-known/openid-configuration discovery endpoint.
For example:
| Provider | Example Issuer URL |
|---|---|
| Keycloak | https://your-host/realms/your-realm |
| PocketID | https://your-host |
Replace these example URLs with the actual addresses supplied by your identity provider.
The My20i Redirect URI and SSO Login URL remain the same regardless of which provider you use.
Troubleshooting OpenID Connect SSO
If you're experiencing difficulties configuring or using SSO, the following checks may help.
| Issue | Possible cause | Resolution |
|---|---|---|
JumpCloud displays invalid_client | Incorrect regional Issuer URL or Client ID | Check your JumpCloud region and Client ID. If necessary, delete and re-add the My20i SSO configuration. |
| JumpCloud reports an invalid Redirect URI | The configured Redirect URI does not match | Ensure the Redirect URI is exactly https://my.20i.com/login/openid. |
| JumpCloud refuses a user's login | The user has not been assigned to the application | Check the application's User Groups tab and ensure the relevant group is selected. |
| Authentication succeeds, but My20i refuses the first login | The user's email does not match their My20i username, or the Email scope is missing | Check the email addresses and ensure the Email scope is enabled. |
| SSO previously worked but now fails | The Subject Claim has changed, or the My20i user has been disabled | Restore the original Subject Claim and verify that the My20i user is active. |
| My20i refuses to save the OIDC configuration | Incorrect Issuer URL or an inaccessible discovery endpoint | Verify the Issuer URL and ensure your provider is accessible over public HTTPS. |
