Okta SSO
Contents
Supported Features
- Single Sign-On (OpenID Connect) initiated via Okta
- Single Sign-On (OpenID Connect) initiated via ByteCompute
- Automatically creates user accounts in ByteCompute on first sign in
Configuration Steps
-
Install the ByteCompute application in your Okta instance
-
Fill in the configuration options:
- Team ID ??your okta subdomain is a great starting point. If you need multiple disjoint teams in the same okta instance a.k.a. multi-tenancy, you can use subdomain-group, for the Team ID. Lowercase only, starting with subdomain, dashes for separators.
- Use Stage ??leave this blank
-
Assign the users or groups that should be able to log into ByteCompute
-
Go to the ByteCompute App (Inside Okta) ??Sign On tab and take note of the Client ID and Client Secret.
-
For the Issuer (normally your okta domain): there should be a section that has a link titled OpenID Provider Metadata. Click this link. In the JSON document shown, look for a key titled "Issuer" and copy the URL-value
-
Send an email to [email protected] that you'd like to setup Okta SSO, including:
- Team ID
- Issuer
- Client ID
- Client Secret
- Admin email ??the email address of the user, who will be admin of the team
-
After the setup is complete the users can start signing in:
- via okta (from dashboard)
- via ByteCompute's sso login, where they need to enter the Team ID
-
The user whose email matches the Admin email specified in the email will become team admin on first login
SP-initiated SSO
The sign-in process is initiated from ByteCompute.
- From your browser, navigate to the ByteCompute login page.
- Click on
Corporate SSObutton. - Enter your Team ID and click
SSO Login - Enter your Okta credentials (your email and password) and click "Sign in with Okta". If your credentials are valid, you are redirected to the ByteCompute dashboard. From there you can click on
Teamto see yourself and the other team members.
Notes
- admin can change team member roles (currently toggle between member and admin)
- admin has access to billing dashboard
- all team members have access to the same api-tokens and models
- if you're interested in single-user-experience --i.e each person having his own tokens and models, let us know!
