Okta Basics

Okta is an identity management service that's used in Labs to provide centralized authentication for Labs applications.

Okta Basics

Currently only Labs Managers have admin access to Okta administration. If you have Okta issues, please reach out to your Engineering Manager.

​Okta is an identity management service that's used in Labs to provide centralized authentication for Labs applications.

We use a centralized identity management service because it is typically the way applications are authenticated in the industry. This gives our students practice using centralized identity management technologies like OAuth and OIDC.

We use Okta specifically because it is an industry leader and has high-quality support and documentation.

Here is a quick walk thru of okta and how it is used in our Labs projects.

The Okta Account

Okta provides centralized identity management. This means that you can have a single set of identities that can be used across many different applications. If you use Google services, you can see this in action as you log in to Google once but can move between Google apps (Mail, Calendar, Sheets, etc.) without having to log in each time.

We use Okta the same way. There is a single Labs Okta account that has a set of identities that can access all Labs applications. These identities are test users that can be used by teams for testing their applications without having to constantly create new identities.

Since Labs applications are always under development, it's very handy to have a set of test identities readily available to test various aspects of your application.

Labs applications should always authenticate using the alias (auth.lambdalabs.dev), though, for reference, the Labs Organization URL is: https://dev-625244.okta.com​

Logging In

As an APL, you'll have access to log in to the Labs Okta account to perform various tasks. Before Labs, you'll receive your login credentials and can use the following link to log in:

​Labs - Sign In​

If you can't login, please contact your engineering manager.

Test Users

A set of test users has been created that teams can use for authentication. These users follow a simple naming convention to make it easy for projects to authenticated.

There are 8 test users, each one using a 3-digit sequence for username and password:

Username	Password	Mailbox
[e-mail]	Test001Test	​https://maildrop.cc/inbox/llama001​
[e-mail]	Test002Test	​https://maildrop.cc/inbox/llama002​
[e-mail]	Test003Test	​https://maildrop.cc/inbox/llama003​
[e-mail]	Test004Test	​https://maildrop.cc/inbox/llama004​
[e-mail]	Test005Test	​https://maildrop.cc/inbox/llama005​
[e-mail]	Test006Test	​https://maildrop.cc/inbox/llama006​
[e-mail]	Test007Test	​https://maildrop.cc/inbox/llama007​
[e-mail]	Test008Test	​https://maildrop.cc/inbox/llama008​

Since the test users are using maildrop.cc for email, you can easily check their inbox if they are meant to receive email notifications from applications.

Please take care never to modify these users in any way! These users are shared across Labs projects, so editing a user can affect other projects.

Administrative Tasks

The following are administrative tasks that you'll need to perform in Okta to support Labs teams.

Retrieve Product Client ID

There is a single Client ID for each product that must be supplied to Labs project teams in order for them to enable authentication. Each product will be set up as an Okta Application. The Client ID can be found using the Admin interface, by clicking on the Applications Tab.

Products have one client id that is shared among all active projects working on that product. Client IDs should not be shared across products.

Issuer URI

The Issuer URI is also required for Labs projects to correctly configure authentication. For Labs projects, this value will always be: https://auth.lambdalabs.dev/oauth2/default​