Skip to main content
Binding a new OIDC identity to a user is a trust decision, so it goes through the same cryptographic verification as OAUTH_LOGIN: the enclave’s Signer independently fetches and verifies the token’s signature against the issuer’s JWKS, and the iss/aud pair must be trusted — either a built-in social provider or an issuer you’ve registered as a Custom OIDC Provider. The oidcToken you submit is re-verified end-to-end; nothing in this request is trusted at face value.
enum<string>
required
Enum options: ACTIVITY_TYPE_CREATE_OAUTH_PROVIDERS_V2
string
required
Timestamp (in milliseconds) of the request, used to verify liveness of user requests.
string
required
Unique identifier for a given Organization.
object
required

The parameters object containing the specific intent data for this activity.

boolean
Enable to have your activity generate and return App Proofs, enabling verifiability.
A successful response returns the following fields:
object
required
The activity object containing type, intent, and result