Okta

1. You are here:
2. IT Business Technology
3. Okta

On this page

• What is Okta?
  • How is GitLab using Okta?
  • What are the benefits to me using Okta as a user?
  • What are the benefits to me as an application administrator to using Okta?
• How do I get my Okta account set up?
  • I want to add Touch ID / Face ID / Face Authentication / YubiKey to Okta
  • I want to add Touch ID / Face ID / Face Authentication to Okta for my mobile device (iPhone/iPad or Android)
  • I want to login or add a new computer to Okta and I have a mobile device enrolled
  • I don't have an enrolled phone or computer but have a YubiKey
  • I would like to get a YubiKey, how can I do so?
  • Lost access to your 2FA or your OKTA account has been locked out because of failed attempts?
• Device Trust
  • Device Trust Setup on macOS
  • After enrolling
• Managing Okta Access Using Google Groups
• Why isn't an application I need available in Okta?
  • How do I get my application set up within Okta?
  • I have an application that uses a shared password for my team, can I move this to Okta?
  • Why does GitLab.com ask for an additional MFA when I login via Okta?
• When adding my GitLab Google Workspace account to my Android device, the biometrics or security key verification never prompts after signing in to Okta.
• Where do I go if I have any questions?

What is Okta?

From the Okta website

Okta is the foundation for secure connections between people and technology. It’s a service that gives employees, customers, and partners secure access to the tools they need to do their most important work.

In practice - Okta is an Identity and Single Sign On solution for applications and Cloud entities. It allows GitLab to consolidate authentication and authorisation to applications we use daily through a single dashboard and ensure a consistent, secure and auditable login experience for all our GitLab team members.

How is GitLab using Okta?

GitLab is using Okta for a few key goals:

• We can use Okta to enable Zero-Trust based authentication controls upon our assets, so that we can allow authorised connections to key assets with a greater degree of certainty.
• We can better manage the login process to the 80+ and growing cloud applications that we use within our tech stack.
• We can better manage the provisioning and deprovisioning process for our users to access these application, by use of automation and integration into our HRIS system.
• We can make trust and risk based decisions on authentication requirements to key assets, and adapt these to ensure a consistent user experience.

What are the benefits to me using Okta as a user?

• A single Dashboard that is provided to all users, with all the applications you need in a single place.
• Managed SSO and Multi-Factor Authentication that learns and adapts to your login patterns, making life simpler to access the assets you need.
• Transparent Security controls with a friendly user experience.

What are the benefits to me as an application administrator to using Okta?

• Automated provisioning and group management
• Ability to transparently manage shared credentials to web applications without disclosing the credentials to users
• Centralised access for users, making it easy to add, remove and change the application profile without the need to update all users.

How do I get my Okta account set up?

All GitLab team-members will have an Okta account set up as part of their onboarding process. You should already have an activation email in both your Gmail and Personal Accounts. For efficiency, please follow the onboarding process for setting up Okta and set up 1Password first and follow that up with Okta. Please also set up Okta from your computer rather than your mobile or the mobile app, as you will be guided to set up the mobile app as part of the onboarding process.

GitLab requires all team members to use either Biometrics or YubiKey as your Okta authentication

I want to add Touch ID / Face ID / Face Authentication / YubiKey to Okta

Using WebAuthn authentication is required for all team members.

1. Touch ID on Mac currently requires Chrome or Safari. The latest version of macOS (Ventura) works better with Touch ID/YubiKeys. There is a known issue with Firefox preventing it from working with Touch ID. YubiKeys can be used with all browsers.

2. While logged in to Okta from the device you wish to add, access the Settings page.
3. In the 'Security Methods' section of the page, choose Set up or Set up another next to Security Key or Biometric.
4. You may then be presented with another prompt to confirm if you wish to Set up another, followed by an Enroll prompt.
5. After pressing Enroll, a prompt from your web browser will appear.

6. For Touch ID or Face ID, choose This Device. For a YubiKey, choose USB security key.

   

7. For Touch ID or Face ID, another prompt will appear asking you to authenticate using Touch ID or Face ID.

   

8. For Security Key, relevant prompts will appear.

   

9. You may be prompted for a PIN, and then finally click Allow.

   

10. We recommend enrolling both Chrome and Safari for redundancy on your computer, as well as a mobile device. Each browser needs to be enrolled separately. Note that separate browser profiles also need to be enrolled separately. You should enroll one computer browser (for example, Chrome), then add the mobile device, then come back and add the other computer browser (for example, Safari).
11. If clearing your browser cache, please be careful as you can delete your Touch ID credential.
    1. In Chrome, if using "Clear Browsing Data" function please ensure that you DO NOT check "Passwords and other sign-in data" (under "Advanced" tab). By default, this is unchecked.
    2. In Safari, the credential is stored under "Settings->Password". This is separate from the "Settings->Privacy" and "Manage Website Data" where you would click "Remove all" to remove the cache.

Follow the GitLab Okta FAQ.

We have also prepared Introductory Videos on Setting up MFA/YubiKeys, Configuring Applications and Dashboard Tips.

I want to add Touch ID / Face ID / Face Authentication to Okta for my mobile device (iPhone/iPad or Android)

These steps are for an iPhone, and may be slightly different for Android. If you are using an iPhone and receive a Developer or XCODE error, please upgrade to iOS 16+. We recommend enrolling a phone even if you don't plan to use it often, in case you need a way to add a new computer or your credential gets accidentally removed on the computer.

1. On the computer, if using Chrome, please check that it is on the latest version by visiting the URL chrome://settings/help - if a new version is available, please use the Relaunch button to restart the browser.
2. On your Mac, please also check that you are using macOS Ventura 13.0.1 or newer.

3. On your Mac, please check under "System Settings"->"Privacy & Security"->"Bluetooth" and make sure that Google Chrome has Bluetooth access enabled.

   

4. On the computer, login into your Okta
5. On the computer, click on your name on the top right to open the drop down menu (similar to above) and navigate to "Settings".
6. On the computer, under Security Methods click "Set up another" beside Security Key or Biometric. This will take you to a setup authentication screen, click "Verify". Provide Touch ID.
7. On the computer, click "Set up", then click "Set up" again on the next screen
8. On the computer, the next step depends on the browser and version.
   1. In Chrome 108+, the pop up that opens states "Create a passkey for gitlab.okta.com" and has your email address listed. Choose "Try another way" at the bottom left.

   

   Then, choose "A different device".

   

   This should display a QR code that you can scan.

   1. In Safari, click "Other options", then choose "iPhone, iPad or Android device - save a passkey on a device with a camera", then "Continue".
9. On the mobile device, open your camera app and scan. (It may take a few seconds for it to connect). This requires Bluetooth to be enabled on both devices, but does not require pairing.
10. On the mobile device, a pop should show up to allow the credential to be saved.
    1. On a iPhone or iPad, it will prompt to save the credential to iCloud Key Chain. Allow this.
    2. If saving the credential fails, go to Settings->your name->iCloud and make sure that Passwords and Keychain is set to "On".
    3. If it still fails, you can also try force restart and then trying to sign out of iCloud on your mobile device, and then sign back in to iCloud.
    4. On Android, this may appear "Use this device with screen lock". Choose this.
11. On the mobile device, attempt to sign in by visiting Okta.

I want to login or add a new computer to Okta and I have a mobile device enrolled

This method has been verified on Macs and Linux with Chrome. For Safari, it requires macOS Ventura 13+. Steps below for iPhone require iOS 16+, may be slightly different for Android.

1. On the computer, log in with username and password
2. On the computer, a popup appears to "Verify your identity with gitlab.okta.com"
3. On the computer, choose "Use phone with a QR code". This requires Bluetooth to be enabled on both the phone and the laptop, but doesn't require pairing.
4. On the mobile device, scan the code using the Camera app
5. On the mobile device, click "Sign in with a Passkey"
6. On the mobile device, a "Sign in" popup appears - "Do you want to sign in to "gitlab.okta.com" with your saved passkey for "xxxxx@gitlab.com"? Click Continue and provide biometric.
7. On the computer, you will now be signed in to Okta.
8. If applicable, follow the standard steps to enroll your Touch ID into Okta.

I don't have an enrolled phone or computer but have a YubiKey

If both of previous devices are not available, you could use a YubiKey as another form of authentication (if you have one set one up). Use that to access your settings page and follow the steps above to enroll a new device.

I would like to get a YubiKey, how can I do so?

Please fill open up the Slack form using /yubikey in a DM to yourself, (check out our guide for some additional information), and we will coordinate shipment of one to you thru our group buy.

Lost access to your 2FA or your OKTA account has been locked out because of failed attempts?

• Head to #it_help in Slack or email it-help@gitlab.com and ask for a 2FA Reset, please be prepared to verify your identity
• Once Okta 2FA is reset please reconfigure it by logging into your Okta account and setting up with either Biometrics or a YubiKey.
• If your account is locked please head to #it_help and ask to have your account unlocked. As a precaution, you will also need to change your Okta Password.

Device Trust

Okta Device Trust ensures that team members are acccessing Okta applications from a managed device. For additional details and timelines, please see the internal handbook.

Device Trust Setup on macOS

1. Open the Okta Verify application on macOS via Spotlight by selecting the magnifying glass in the menu bar (top right corner of display). Another method to open Spotlight is to use cmd + Space

2. Search for Okta Verify

3. Select Get Started

4. Select Next

5. Confirm gitlab.okta.com is populated for Sign-in URL and then select Next

6. A browser window will open to gitlab.okta.com to confirm your identity

7. After doing so, you will see the Your Identity is Verified message and you can close the browser

8. The Okta Verify application will refresh. Press Next if you are using Touch ID on your Mac (most common), or Skip if you are not. Okta Verify uses macOS's Touch ID capability, and the mathematical calculation is stored locally within Apple's Secure Enclave and not available to Okta or GitLab.

9. If you pressed Next, then click Enable Touch ID

10. Your GitLab Okta account will now be available to use with Okta Verify on macOS

After enrolling

You will continue to be able to use a YubiKey in addition to Touch ID to login to Okta from macOS device. You will not be able to login from a personal macOS device.

A macOS device missing the certificate (even when enrolled with Okta Verify), will quickly show:

Then re-direct to the following error:

Managing Okta Access Using Google Groups

The GitLab Team Member Enablement team has created a new process for Owners and Provisioners to manage access to Okta applications. If you are listed as an Owner/Provisioner for an application in the tech stack you will be using the method below to add users to a Google group, which will then sync this group to Okta and assign the application to users. This process was created to empower business application owners to effect Access Requests which require Okta application assignment.

• Sign in to Google Groups.
• Click My groups.
• Click the name of the group were you want to add/remove a user. (Note that all Google groups which manage users in Okta application start with okta-xxxxx-users)

• Next press the People tab on the left side and select Members.

• This will show you all the members currently in the group.
• To add a member press the Add Members button. To remove access mouse over a user and press on the little white box that appears, this will mark the user. After that on the right side press the remove member button (Looks like a circle with a horizontal line across).

When a member is added/removed from the group it may take up to 1 hour for the sync to happen between Google and Okta. Once the sync happens the user will see the application in Okta, if removed the opposite. If you have any questions or require assistance please reach out to the IT team in the #it-help Slack channel.

Why isn't an application I need available in Okta?

Create a new application setup issue and fill in as much information as you can.

Okta is currently configured with assigned groups/roles based on a team member's role/group. Refer to the Access Change Request section of the handbook for additional information on why an application may not be available in Okta.

How do I get my application set up within Okta?

If you are an application owner please submit a new application setup issue on the Okta project page for your application. We will work with you to verify details and provide setup instructions.

I have an application that uses a shared password for my team, can I move this to Okta?

Yes you can! Submit a new application setup issue on the Okta project page for your application. We will work with you to verify details and provide setup instructions.

If you are having problems with being asked for multiple MFA authentications during the day, please log an issue and we can look into it.

Why does GitLab.com ask for an additional MFA when I login via Okta?

Your gitlab.com account will have 2FA installed as required by our policy. Note that the 2FA for GitLab.com is different to the MFA you use to log into Okta. This issue has been opened to propose a solution.

When adding my GitLab Google Workspace account to my Android device, the biometrics or security key verification never prompts after signing in to Okta.

When attempting to add a Google Workspace account to an Android device, Okta authentication proceeds in the Android's embedded browser (WebView).

Since Okta does not support embedded web browsers for WebAuthn based verification, which causes an issue where nothing prompts you after you sign-in to Okta, so you cannot add the Google Workspace account to Android devices.

Please reach out to #it_help Slack channel to request temporary enable Okta Verify as a workaround.

Where do I go if I have any questions?

• For Okta help, setup and integration questions: #it_help slack channel