Create Credential Challenge
Part of the flow Create Credential Regular flow.
Starts a create user credential session, returning a challenge that will be used to verify the user’s identity.
Authentication
✅ Organization User (CustomerEmployee)✅ Delegated User (
EndUser)❌ Personal Access Token not allowed
❌ Service Account
Required Permissions
No permission required.Authorizations
Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
Body
The kind of credential.
Fido2, Key, RecoveryKey, PasswordProtectedKey Response
Success
- Fido2/Passkeys
- Public/Private key pair
- Password-protected Key
- Recovery Credentials
- <Deprecated> Password
- <Deprecated> TOTP
Fido2 Credential, also known as Passkeys or WebauthN credential.
Fido2 Challenge identifier to be used in the subsequent create credential request.
Challenge value to be signed by the credential.
Identifies the information needed to verify the user's signing certificate; can be one of the following:
- none: indicates no attestation data is required
- indirect: indicates the attestation data should be given, but that it can be generated using an Anonymization CA
- direct: indicates the attestation data must be given and should be generated by the authenticator
- enterprise: indicates the attestation data should include information to uniquely identify the user's device
none, indirect, direct, enterprise @deprecated use challengeIdentifier instead