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.
GitLab is using Okta for a few key goals:
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 Okta Verify mobile app as part of the onboarding process.
GitLab requires all team members to use either Biometrics or YubiKey as your Okta authentication
Using WebAuthn authentication is required for all team members.
Set up or Set up another next to Security Key or Biometric.Set up twice, a prompt from your web browser will appear, or a 1Password prompt may appear. Click the “YubiKey” icon to bypass if it appears and you wish to save it in iCloud Keychain (recommended) or the local Chrome browser.
For iCloud Keychain or a YubiKey, click “Use a different passkey”. For the local Chrome browser choose “Continue”.
If you choose to save it in your Chrome profile, another prompt will appear asking you to authenticate using Touch ID or Face ID.
If you chose to use the iCloud Keychain or Security Key, choose the correct option to finish enrollment.
For Security Key, relevant prompts will appear.
You may be prompted for a PIN, and then finally click Allow.
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, unless you use iCloud Keychain. Note that separate Chrome browser profiles also need to be enrolled separately. You should enroll one computer browser (for example, Chrome), then add the mobile device, then if required add the other computer browser (for example, Safari).
If clearing your browser cache, please be careful as you can delete your passkey.
Follow the GitLab Okta FAQ.
We have also prepared Introductory Videos on Configuring Applications and Dashboard Tips.
With the 1Password browser extension installed, access the Settings page.
In the ‘Security Methods’ section of the page, choose Set up or Set up another next to Security Key or Biometric.
You may then be presented with another prompt to confirm if you wish to Set up another, followed by an Enroll prompt.
After pressing Enroll, a prompt from your web browser will appear.
From 1Password, you’ll see a pop up notification from 1Password with the options “New Item” or “Update Existing”. Select “Update Existing” and your Okta account to continue.
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.
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.
On your Mac, please also check that you are using macOS Ventura 13.0.1 or newer.
On your Mac, please check under “System Settings”->“Privacy & Security”->“Bluetooth” and make sure that Google Chrome has Bluetooth access enabled.
On the computer, login into your Okta
On the computer, click on your name on the top right to open the drop down menu (similar to above) and navigate to “Settings”.
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.
On the computer, click “Set up”, then click “Set up” again on the next screen
On the computer, ignore all popups from the 1Password browser extension as it could interfere with the process of transferring the passkey. Click the “Yubikey” icon to bypass if it appears.
On the computer, the next step depends on the browser and version.
Then, choose “Use a phone, tablet or security key”.
This should display a QR code that you can scan.
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.
On the mobile device, a pop should show up to allow the credential to be saved.
your name->iCloud and make sure that Passwords and Keychain is set to “On”.On the mobile device, attempt to sign in by visiting Okta.
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.
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.
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.
#it_help in Slack or email it-help@gitlab.com and ask for a 2FA Reset, please be prepared to verify your identity#it_help and ask to have your account unlocked. As a precaution, you will also need to change your Okta Password.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.
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
Search for Okta Verify
Select Get Started
Select Next
Confirm gitlab.okta.com is populated for Sign-in URL and then select Next
A browser window will open to gitlab.okta.com to confirm your identity
After doing so, you will see the Your Identity is Verified message and you can close the browser
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.
If you pressed Next, then click Enable Touch ID
Your GitLab Okta account will now be available to use with Okta Verify on macOS
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:
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.
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.
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.
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.
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 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.
#it_help slack channel6f138007)
