Skip to main content

OktaShared Signals with Okta Identity Threat Protection Beta

License requirements

Receiving shared signals in Okta requires Okta Identity Threat Protection with Okta AI on Okta Identity Engine. On the XFA side, Shared Signals is in beta and turned on per organization on request (see the overview).

Note: This guide assumes that you have an account set up with XFA for your organization and that you're an administrator for that organization in XFA. In Okta you need the super administrator role, or a custom admin role that can manage Shared Signals Framework receiver streams. If you do not have an XFA account, you can create one at https://dashboard.xfa.tech/signup.

Okta receives shared signals by push. XFA sends a CAEP device-compliance-change event to your Okta org every time a device of your organization changes between compliant and not compliant (see what "not compliant" means). Okta matches the event to the user by email and applies its own policies.

There is no token to exchange. You tell XFA the address of your Okta org, and you tell Okta XFA's well-known URL. Okta checks every event against XFA's public signing key.

1. Add the Okta connection in XFA

  1. In the XFA dashboard, open Device security > Shared Signals.
  2. Click Add connection.
  3. Enter a Name, for example Okta production, and choose Okta as the Receiver.
  4. Enter your Okta org URL, for example https://acme.okta.com. Use only the address of the org, without a path.
  5. Click Add connection.

XFA creates the stream to your Okta org right away. The connection shows that XFA pushes to your Okta org, and its stream is listed under it.

In the Transmitter section at the top of the page, copy the Well-known configuration URL:

https://ssf.xfa.tech/.well-known/ssf-configuration

2. Add XFA as a transmitter in Okta

  1. In the Okta Admin Console, go to Security > Device Integrations and open the Receive shared signals tab.
  2. Click Create stream.
  3. Enter an Integration name, for example XFA.
  4. Choose to set it up with a Well-known URL, and paste the Well-known configuration URL from the previous step.
  5. Click Create.

The stream appears in Okta's list with the status Active. Okta can also be set up with the Issuer URL and JWKS URL instead; both are shown in the Transmitter section of the Shared Signals page.

The stream covers every user of your organization. Okta only acts on events for users it knows, matched by email.

3. Decide what Okta does with the event

A device-compliance-change event carries the user (email), the device (an opaque XFA device identifier), the previous and current status (compliant or not-compliant), the time of the evaluation and the failing checks in the reason fields.

Okta does not act on the event by itself. It records the event in the System Log and feeds it into the entity risk of the user, and your Okta policies decide the response: for example an entity risk policy rule that signs the user out of all sessions, or a session policy that requires re-authentication. Configure those under Security in the Okta Admin Console. XFA sends the event; the enforcement is Okta's.

4. Verify with a test event

  1. On the Shared Signals page in XFA, find the stream under your Okta connection and click Send test event.
  2. XFA pushes an SSF verification event to your Okta org and shows the result of the delivery on the stream.
  3. In Okta, check the System Log for the event received from XFA.

A real device-compliance-change event follows within minutes of a device changing state: let a device of a test user fail a check that blocks in a policy attached to one of your applications, and the event shows in the Okta System Log.

Troubleshooting

  • Okta cannot create the stream: check that the well-known URL is exactly https://ssf.xfa.tech/.well-known/ssf-configuration. Okta asks you to check the URL and add the stream again when creation fails.
  • The stream in XFA shows a failed delivery: the stream shows the error Okta returned. Check that XFA was added as a stream in the same Okta org whose URL you entered in XFA, and that the stream in Okta is active. Deliveries are retried on temporary errors.
  • The Okta org URL in XFA is wrong: remove the connection and add it again with the right URL. The URL of an Okta connection cannot be changed.
  • No events arrive: a device only sends an event when its state changes. Check that the failing check is set to block in a policy that is attached to an application, and that the user's email in XFA matches the email in Okta.
  • Nothing happens in Okta after an event: Okta logged the event but no policy acted on it. Review your entity risk and session policies.