> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/integrations/integration-fundamentals/identity-integrations/okta-ssf.md).

# Okta SSF

Material integrates with Okta using the Shared Signals Framework (SSF). This SSF integration enhances security by sending notifications to your Okta instance whenever user risk reports are created or updated in Material.

To set up your integration, complete a few steps in both Material and in Okta.

{% hint style="success" %}
Before you begin, open a tab in Material and Okta each to work in both concurrently.
{% endhint %}

## How to integrate with Okta SSF

### Part One: Create a new Okta Integration in Material

#### **Create an Okta Admin**

{% hint style="warning" %}
Always review Okta's documentation directly for up to date instructions.
{% endhint %}

1. In Okta, create a new Okta admin (e.g. "Material Admin") and assign the required roles based on selected capabilities.
   1. **Groups** - Group, Help Desk, App, or Read Only Admin
   2. **MFA Status** - App or Read Only Admin
   3. **End-User Verification** - Help Desk Admin Log in to your Okta organization as the new admin.
2. From the **Security** menu, select API then select **Tokens**.
3. Click **Create Token**.
4. Name your token (e.g. "Material") and click **Create Token**.

{% hint style="danger" %}
Copy your API token because you will only see it one time.
{% endhint %}

#### **Create a new integration in Material**

5. From the top toolbar, click **Integrations**.
6. Click **Create Integration**.
7. Under **Identity**, choose **Okta SSF**.
8. Click **Create new integration**.

<figure><img src="/files/zq9s2Wre5dRhgciJ3h8J" alt=""><figcaption></figcaption></figure>

9. Complete the required fields:
   1. **Org** **URL**: your complete Okta Org URL (e.g. <https://acme.okta.com>)
   2. **Token:** The token you created in step 4.
10. Confirm **Shared Signals Framework (SSF)** is checked.
11. Click **Add Event** to choose the event(s) that will trigger your stream.

    <figure><img src="/files/u8cbgmXIt8rtCRJE2L4X" alt=""><figcaption></figcaption></figure>

<details>

<summary>How to choose events</summary>

Use the form to build the trigger based on multiple filters.

* The most common event used is `Issue Change` . It covers most needs.
* Other common filters are:
  * **Severities**: trigger based on an issue severity change
  * **Detection**: trigger based on a specific detection
* Choose the option to **Include events for messages being added / removed / interacted with in a phishing case** if you want to also trigger based on individual message level changes (rather than just issue level changes).

***

* While you can include multiple events in one integration, you can only include one of each event type (i.e. one issue change, etc.) All the filters must match to trigger the event. If you need to trigger webhook using OR logic, create multiple integrations with different event parameters.

<figure><img src="/files/gcmSUUqhfuYzcEZh6NMc" alt="" width="336"><figcaption></figcaption></figure>

* Toggle events off/on at any time in the integration view.
* Once your webhook starts firing, the last time an event triggered is included in the integration view, under **Events**:

<figure><img src="/files/duhYtIhHFCG1fnrA2LyH" alt=""><figcaption></figcaption></figure>

</details>

12. Copy the **Material Outbound IPs.**
13. **Save** the integration.

#### In Okta, create an IP Zone

12. Navigate to **Security** > **Networks** then click **Add Zone** to create a new **IP Zone**.
13. Name the zone and paste the **Outbound IPs** from Material (step 12) into the **Trusted Proxy IPs** field. This lets Okta display the correct geographic location during identity verification.
14. Click **Save** in Okta to save the IP Zone.

### Part Two: Set up an OKTA SSF receiver

#### Create a stream in Okta

15. In Okta, select **Security >** **Device Integrations > Receive shared signals**.
16. Click **Create Stream**.
17. Enter a **name for the stream** (e.g. "Material SSF Stream")
18. Select **Well-known URL**:
19. In Well-known URL field, paste: `https://<your-material-instance>/.well-known/ssf-configuration/ssf/okta/<your-stream-id>`
20. Click **Create.** This validates Okta is able to communicate with Material. If this is successful it will close the modal.
    1. If an error occurs, the integration likely isn't enabled on the Material side. Return to steps 5-13 and confirm you **Saved.**
21. Your receiver should now display in Okta:

    <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf4qHJEDIuYu5mT24-f3cezWWQkYwV9uDUfEfMQrDrZekbxE9ANaBPwqlvelrsM8GDpT4xQGIBuUzN7xLA501q1YH5mYmRxirYvGnO4xDN3emk1OsesAmmVa8G6ZdYP23s4QhoaXA?key=juRqjLD1YbhZXWY0_ziSgw" alt=""><figcaption><p>Your receiver displays in Okta</p></figcaption></figure>

### Wrap-up

Now the event subscription is created and Okta will start receiving User Risk Report Change events from Material for issue change events (create and update). In the **Okta System Log**, you will see events like this:

<figure><img src="/files/aS87zj5QM6aAiAeqm4kL" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.material.security/integrations/integration-fundamentals/identity-integrations/okta-ssf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.