An HTTP 400 error occurs when listing identity source sessions because the profile sourcing feature remains inactive in the Custom Identity Source application. Enable the profile sourcing feature in the application provisioning settings to resolve the error.

When attempting to set up a new Anything-as-a-Source (XaaS) Custom Identity Source application, Okta generates an HTTP 400 error code for the following API call:

GET /api/v1/identity-sources/{id}/sessions

(Okra specific) E0000001: Api validation failed: Identity Source App — Please enable profile sourcing feature.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Custom Identity Source Application
• Okta Integration Network (OIN)
• Identity Source Session API

The profile sourcing feature remains inactive in the corresponding Custom Identity Source application.

How is the profile sourcing feature enabled for a Custom Identity Source application?

Navigate to the application provisioning settings in the Okta Admin Console, enable the profile sourcing feature, and rerun the API call.

1. In the Okta Admin Console, navigate to Applications > Applications.
2. Select the Custom Identity Source application.
3. Navigate to the Provisioning tab and select To Okta in the left settings menu.
4. Click Edit.
5. Enable the Profile Sourcing feature by selecting the Allow Custom Identity Source to source Okta users checkbox.

6. Review and optionally configure the When a user is deactivated in the app option.
7. Review and optionally configure the When a user is reactivated in the app option.
8. Click Save.
9. Rerun the List all identity source sessions API call to complete the request with an HTTP 200 OK success code.

   GET /api/v1/identity-sources/{id}/sessions

Related References

• Custom Identity Source
• Identity Source API
• Anything-as-a-Source Guide
• List All Identity Source Sessions