-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: update Okta Documentation for SAML (#1634) DOC-884
* Update Okta Documentation for SAML * Optimised images with calibre/image-actions * Fix spelling * Fix spelling * Update Okta SAML Documentation - renamed all files based on standard - separated oidc / saml documentation - added validation / team creation for okta saml * docs: fixed images names and prevented redirect need --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Karl Cardenas <[email protected]>
- Loading branch information
1 parent
3906683
commit 9909d5d
Showing
9 changed files
with
196 additions
and
17 deletions.
There are no files selected for viewing
178 changes: 178 additions & 0 deletions
178
docs/docs-content/user-management/saml-sso/palette-sso-with-okta-saml.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,178 @@ | ||
--- | ||
sidebar_label: 'Palette SSO with Okta SAML' | ||
title: 'Enable SSO with Okta SAML' | ||
description: 'Set up Palette SSO with Okta SAML' | ||
icon: "" | ||
hide_table_of_contents: false | ||
sidebar_position: 30 | ||
hiddenFromNav: false | ||
tags: ["user-management", "saml-sso", "okta"] | ||
--- | ||
|
||
Single Sign-On (SSO) is an authentication method that enables users to log in to multiple applications and websites with one set of credentials. SSO uses certificates to establish and maintain a trust relationship between the Service Provider (SP) and an Identity Provider (IdP). Palette supports SSO based on either the Security Assertion Markup Language (SAML) or OpenID Connect (OIDC). | ||
|
||
The following steps will guide you on how to enable Palette SSO with [Okta Workforce Identity Cloud](https://www.okta.com/products/single-sign-on/) based on SAML. | ||
|
||
|
||
## Prerequisites | ||
|
||
- You need to have either a free or paid subscription with Okta. Okta provides free [developer subscriptions](https://developer.okta.com/signup/) for testing purposes. | ||
|
||
|
||
## Enablement | ||
|
||
### Create Teams in Palette | ||
|
||
This step is to create teams in Palette that will be used for Okta SAML, this will give them the appropriate permissions. For this example, you will create the `Okta Team` team and give it **Tenant Admin** permissions. You can repeat this for any other team that you configured with group claims. | ||
|
||
1. Open a web browser and navigate to your Palette subscription. Navigate to **Tenant Settings** --> **Users & Teams** --> **Teams** tab, and click **+ Create Team**. | ||
|
||
![Create Palette Team](/palette-sso-with-adfs-images/how-to_palette-sso-with-adfs_create-team.png) | ||
|
||
<br /> | ||
|
||
2. Specify `Okta Team` in the **Team name** field. You don't need to set any members now, as this will happen automatically from the SSO. Click **Confirm** to create the team. | ||
|
||
![Name Palette Team](/palette-sso-with-adfs-images/how-to_palette-sso-with-adfs_name-team.png) | ||
|
||
<br /> | ||
|
||
3. The list of teams displays again. Select the newly created **Okta Team** team to review its details. To give this team administrative access to the entire tenant and all the projects in it, assign the **Tenant Admin** role. Select **Tenant Roles** and click **+ Add Tenant Role**: | ||
|
||
![Palette Tenant Roles](/palette-sso-with-adfs-images/how-to_palette-sso-with-adfs_tenant-roles.png) | ||
|
||
<br /> | ||
|
||
4. Click on **Tenant Admin** to enable the role. Click **Confirm** to add the role. | ||
|
||
![Add Tenant Role](/palette-sso-with-adfs-images/how-to_palette-sso-with-adfs_add-tenant-role.png) | ||
|
||
<br /> | ||
|
||
You will receive a message stating **Roles have been updated**. Repeat this procedure for any other teams, taking care to ensure they are given the appropriate permissions. | ||
|
||
5. Click the **X** next to **Team Details** in the top left corner to exit this screen. | ||
|
||
### Create the Okta Application | ||
|
||
1. Log in to your Okta Admin console and navigate to **Applications** --> **Applications**. Click the **Create App Integration** button. | ||
|
||
<br /> | ||
|
||
:::info | ||
|
||
Your Okta login URL has the following format, | ||
`https://{your-okta-account-id}-admin.okta.com/admin/getting-started`. | ||
Replace `{your-okta-account-id}` with your Okta account ID. | ||
|
||
::: | ||
|
||
<br/> | ||
|
||
2. In the screen that opens, select **SAML 2.0** for the sign-in method. Then click **Next**. | ||
|
||
<br /> | ||
|
||
![Create Okta Application](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_create-application.png) | ||
|
||
<br /> | ||
|
||
1. The following screen allows you to configure the new App Integration. On the **App name** field, change the name from `My Web App` to `Spectro Cloud Palette SAML`. If desired, you can also upload a logo for the application. | ||
|
||
<br /> | ||
|
||
![Configure Okta General Settings](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_general-settings.png) | ||
|
||
<br /> | ||
|
||
4. Open a web browser and navigate to your Palette subscription. Navigate to **Tenant Settings** --> **SSO** and click **SAML**. Click the button next to **Login URL** to copy the value to the clipboard. | ||
|
||
5. Set the value of **Service** to **Okta**. | ||
|
||
<br /> | ||
|
||
![Configure General SSO Settings](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_palette-manage-sso-okta-saml.png) | ||
|
||
<br /> | ||
|
||
6. Switch back to your Okta Admin console and paste the copied value to the **Single sign-on URL** and **Audience URI (SP Entity ID)**. | ||
|
||
7. Specify values within **Attribute Statements** and **Group Attribute Statements** to link user values from Okta to SpectroCloud. | ||
|
||
Under **Attribute Statements (Optional)** specify the below values. | ||
|
||
| Name | Name Format | Value | | ||
| -- | -- | -- | | ||
| `FirstName` | `Unspecified` | `user.firstName` | | ||
| `LastName` | `Unspecified` | `user.lastName` | | ||
| `Email` | `Unspecified` | `user.email` | | ||
|
||
Under **Group Attribute Statements (Optional)** specify the below values. | ||
|
||
| Name | Name Format | Filter | Value | | ||
| -- | -- | -- | -- | | ||
| `SpectroTeam` | `Unspecified` | `Matches Regex` | Blank | | ||
|
||
<br /> | ||
|
||
![Configure Attribute Statements](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_attribute-statements.png) | ||
|
||
<br /> | ||
|
||
8. Finish the creation of the application with default values. | ||
|
||
9. Once brought to main application page, copy the **Metadata URL**, open it up in a separate page, then copy of the contents of the XML. | ||
|
||
<br /> | ||
|
||
![Copy Okta SAML Metadata](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_metadata-url.png) | ||
|
||
<br /> | ||
|
||
10. Go back to Palette SSO settings then paste the contents of the Okta SAML Metadata into **Identity Provider Metadata**. | ||
|
||
<br /> | ||
|
||
![Paste Metadata in Palette SSO Manager](/saml-okta-images/user-management_saml-sso_palette-sso-with-okta-saml_palette-manage-sso-okta-saml.png) | ||
|
||
<br /> | ||
|
||
11. Under **Default Teams**, search for then click the Palette team we created called **Okta Team**. This connects all Okta users with the team and the team permissions we set earlier. | ||
|
||
12. When all the information has been entered, click Enable to activate SSO. You will receive a message stating SAML configured successfully. | ||
|
||
### Validate | ||
|
||
1. Log in to Palette through SSO as an Okta user who is a member of the Okta application to verify SSO. If you are still logged into Palette with a non-SSO user, log out by selecting **Logout** in the **User Menu** at the top right. | ||
|
||
<br /> | ||
|
||
![User Logout](/oidc-okta-images/oidc-okta_user-logout.png) | ||
|
||
<br /> | ||
|
||
|
||
2. The Palette login screen now displays a **Sign in** button and no longer presents a username and password field. Below the **Sign In** button, there is an **SSO issues? --> Use your password** link. This link can be used to bypass SSO and log in with a local Palette account in case there is an issue with SSO and you need to access Palette without SSO. Click on the **Sign in** button to log in via SSO. | ||
|
||
<br /> | ||
|
||
![User SSO Login](/oidc-okta-images/oidc-okta_palette-login.png) | ||
|
||
<br /> | ||
|
||
3. If this is the first time you are logging in with SSO, you will be redirected to the Okta login page. Depending on your organization's SSO settings, this could be a simple login form or require MFA (Multi-Factor Authentication). | ||
|
||
<br /> | ||
|
||
4. You are now automatically added to the `Okta Team` team in Palette. To verify, navigate to the left **Main Menu**, select **Tenant Settings** --> **Users & Teams** --> **Teams** tab. Click on the **Okta Team** team and view the team members section. | ||
|
||
|
||
## Resources | ||
|
||
- [Okta Workforce Identity Cloud](https://www.okta.com/products/single-sign-on/) | ||
|
||
|
||
- [Palette User Management](../user-management.md) | ||
|
||
|
||
- [Palette SSO](saml-sso.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file added
BIN
+73 KB
...es/user-management_saml-sso_palette-sso-with-okta-saml_attribute-statements.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+65.4 KB
...ages/user-management_saml-sso_palette-sso-with-okta-saml_create-application.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+86.6 KB
...images/user-management_saml-sso_palette-sso-with-okta-saml_general-settings.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+105 KB
...kta-images/user-management_saml-sso_palette-sso-with-okta-saml_metadata-url.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+197 KB
...gement_saml-sso_palette-sso-with-okta-saml_palette-manage-sso-okta-metadata.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+146 KB
...management_saml-sso_palette-sso-with-okta-saml_palette-manage-sso-okta-saml.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.