POST /auth /registration /social
By using POST /auth API, you can start an end-user registration session by passing a JWT obtained by an IdP. It returns a challenge that will need to be signed by a passkey and is used to perform the complete end user registration with wallets.
- Authentication
- No authentication required.
- Required Permissions
- No permissions required.
- Parameters
-
socialLoginProviderKind: Available options: Oidc
idToken
orgId
- Request body
-
{ curl --request POST \ --url https://api.digitalassets.ibm.com/auth/registration/social \ --header 'Content-Type: application/json' \ --data '{ "orgId": "<string>", "socialLoginProviderKind": "Oidc", "idToken": "<string>" }' - Response
- 200: Success
{ "user": { "id": "<string>", "displayName": "<string>", "name": "<string>" }, "temporaryAuthenticationToken": "<string>", "challenge": "<string>", "supportedCredentialKinds": { "firstFactor": [ "Fido2" ], "secondFactor": [ "Fido2" ] }, "authenticatorSelection": { "residentKey": "required", "requireResidentKey": true, "userVerification": "required", "authenticatorAttachment": "platform" }, "attestation": "none", "pubKeyCredParams": [ { "type": "public-key", "alg": 123 } ], "excludeCredentials": [ { "type": "public-key", "id": "cr-6uunn-bm6ja-f6rmod5kqrk5rbel" } ], "otpUrl": "<string>", "rp": { "id": "<string>", "name": "<string>" } }