# Okta SSO Setup

{% hint style="info" %}
Netacea will supply you with the following before you start:

* `Single sign-on URL`
* `Audience URI (SP Entity ID)`
  {% endhint %}

## Configuration <a href="#configuration" id="configuration"></a>

* Go to the Okta application and Sign in
* Go to the `Applications` and click on `Create App Integration`

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FnAIabhCMFcxaUYker4fw%2Fimage.png?alt=media&#x26;token=ed701dc4-e960-438c-9b99-539342bca833" alt=""><figcaption></figcaption></figure>

* Select `SAML 2.0` and click on `Next`

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FcFQzfGVpRWA9Y31c2AvB%2Fimage.png?alt=media&#x26;token=c820700b-d57b-4374-8f48-ba7343fe9a3d" alt=""><figcaption></figcaption></figure>

* Landed to `Create SAML Integration` > `General Settings` Fill the following fields
  * `App name` : `Netacea Portal (PROD)`
  * Do not check the `App visibility` and click on `Next`

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FaZvYUn8wg9NvjsFWPnm6%2Fimage.png?alt=media&#x26;token=b9690c80-2c01-425e-9ea7-fe6ec68c33da" alt=""><figcaption></figcaption></figure>

* `SAML Settings`
  * Paste the `Single sign-on URL`
  * Paste the `Audience URI (SP Entity ID)`
  * Select `EmailAddress` in the `Name ID format` field
  * Select `Email` in the `Application username`
  * Select `Create and update` in the `Update application username on` field
  * Select `Signed` in the `Response` field

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FqUwIVVPFQwbGVoVdour8%2Fimage.png?alt=media&#x26;token=6ee2af15-4d7b-4d8d-86d2-83757e2d33e0" alt=""><figcaption></figcaption></figure>

* Add `Attribute Statements` as follows

These data mappings are used to correctly display usernames, send portal notifications to associated email addresses, and are used in Netacea’s Audit Trail feature to identify which actions were taken by who and when. User mappings are created automatically when a user logs into the Netacea Portal via SSO - and can be removed either by request, or through the User Management section of Netacea’s Portal.

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2F29WJwj4Su9any3b0Ig06%2Fimage.png?alt=media&#x26;token=155d0d85-10d2-46ad-aae6-2ca543ca528d" alt=""><figcaption></figcaption></figure>

* Leave any other fields and keep them to their default values
* Click on `Next`

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FGiJgwJbOZGPvwjwy41n4%2Fimage.png?alt=media&#x26;token=ca7a7df4-a2bb-4b4f-b459-553cfe3156d7" alt=""><figcaption></figcaption></figure>

* **Select** the `App type` checkbox and then **click** on `Finish`
* **Select** the `Sign on` Tab and **copy** the `Metadata URL` value from App and provide this to the Single Sign On setup form in the Netacea Portal

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FBocK2jn3GTeDCNbGZ5bc%2Fimage.png?alt=media&#x26;token=6647cc30-c2be-4977-a10c-c5eca8f95fe0" alt=""><figcaption><p>Copy the Metadata URL so it can be pasted into the Netacea SSO setup page.</p></figcaption></figure>

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FEDu16A3MRUax2VPpO6dZ%2Fimage.png?alt=media&#x26;token=168352d2-4fb4-4939-8277-bc553ae44ede" alt=""><figcaption><p>In the Netacea Portal, provide the IDP Configuration settings from the Okta form</p></figcaption></figure>

* Populate the `Attribute Mappings` using the `Attribute Statements` from Okta:
  * Given Name Attribute
    * In the example above, the value is `given_name`
  * Family Name Attribute
    * In the example above, the value is `family_name`
  * Email Address Attribute
    * In the example above, the value is `email`

## Testing <a href="#testing" id="testing"></a>

{% hint style="info" %}
It is recommended to configure SSO in a separate incognito mode window of your browser. This way, you keep the session in the standard window, allowing you to switch off the SSO authorization in case something is misconfigured.
{% endhint %}

* Visit: <https://portal.netacea.com>

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FU33MXxWSibY6VTWbVVmA%2Fimage.png?alt=media&#x26;token=d56da01a-68f3-4b65-85ff-a91dd75e33c6" alt="" width="491"><figcaption></figcaption></figure>

* Select **Enterprise SSO Login**
* Login using a valid email address associated with the **Okta** application.

<figure><img src="https://2843832198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FznjHsCCFk9N601bmryTK%2Fuploads%2FQ5L3Old9Gcfs3MRoim9O%2Fimage.png?alt=media&#x26;token=50393caf-4bbd-4e45-ad06-de5303d26162" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Check out the [FAQs ](https://netacea.gitbook.io/portal-docs/user-management/single-sign-on-sso/sso-faqs)for answers to some common issues
{% endhint %}
