Create a JSON Web Token by passing an identity and password

This is used to log in with an identity and password. The resulting Jwt specifies the header name and header value that should be passed on all subsequent requests to identity the caller. Tokens expire need to be renewed. Any request with an expired token will return an HTTP 401 error and should be renewed. Best practice is to store the expiry date and renew before the token expires. Catching expiry errors and then deciding to renew and retry the request is often error prone.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

A username/password (and optional challenge response for WebAuthN/PKI auth) and/or TOTP for getting a valid JWT

string
length between 44 and 44

Optional: Needed when identity has a public key or responding to a WebAuthN challenge

string
length between 44 and 44

Optional: Needed when identity has a public key or responding to a WebAuthN challenge

string
length ≤ 200
string
required
length between 3 and 40

Identity/username for authentication

string
length between 6 and 6

Optional: Needed when wanted to impersonate users with otp by a currently authenticated user - the currently authenticated user must contain a position for allowing impersonation. Also required if device fingerprinting is enabled on the tenant and the fingerprint is not enrolled

string
required
length between 3 and 80

Can be pre-hashed with BCRYPT or passed as clear text in which case Eclipse will hash it

securityQuestionAnswers
array of objects

Optional: Needed if the customer has security questions

securityQuestionAnswers
string
length between 6 and 6

Optional: Needed when identity has MFA enabled. This is the time based OTP for the identity

Responses

400

Bad Request

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json