Test validates an SSF receiver stream’s configuration by checking JWKS reachability, identity resolution, and action preview without processing real events.
Documentation Index
Fetch the complete documentation index at: https://conductorone-groman-network-requirements-updates.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
The ID of the SSF receiver stream to test.
SSFReceiverStreamServiceTestRequest identifies the stream to test and an optional subject for identity resolution validation.
The upstream identifier to test resolution with. Typically an email address (e.g., "alice@company.com") — the same value the IdP would send in a SET subject. The Test RPC runs resolveSubject on this to verify the identity mapping works. Optional: upstream identifier (email) to test identity resolution. If empty, only JWKS reachability is tested.
SSFReceiverStreamServiceTestResponse reports the results of the stream configuration test across JWKS, identity, and action readiness checks.
SSFReceiverStreamServiceTestResponse reports the results of the stream configuration test across JWKS, identity, and action readiness checks.
Number of active refresh tokens for the matched user that would be affected.
Number of active sessions for the matched user that would be affected.
Step 3: Action preview. The action configured for session-revoked events on this stream.
SSF_REVOCATION_ACTION_UNSPECIFIED, SSF_REVOCATION_ACTION_REVOKE_ALL, SSF_REVOCATION_ACTION_LOG_ONLY Step 2: Identity mapping. Whether the test subject was resolved to a ConductorOne user.
Error message if the JWKS endpoint could not be reached or returned invalid data.
Number of signing keys found at the JWKS endpoint.
Step 1: JWKS reachability. Whether the JWKS endpoint was reachable and returned valid keys.
The ConductorOne user ID the test subject maps to, if an identity link was found.
Overall readiness. Whether the stream passed all test checks and is ready to process events.
The upstream IdP subject identifier (e.g., Okta user ID "00u1234") resolved from the test subject.