Login
Authenticates a user against Installer and starts a session. This is the entry point for all other Installer APIs - every subsequent request must present the credentials returned here.
How to use the response:
- On success, the
Set-Cookieresponse header contains the session cookie and theX-XSRF-TOKENresponse header contains the XSRF token. Send the cookie value in theCookierequest header and the token value in theX-XSRF-TOKENrequest header on every subsequent request. - The
rolesreturned in the response body determine which of the other Installer APIs this user is authorized to call (see thesecurityrequirements on each operation).
Notes:
- If the user's password has expired, the API returns
302and redirects to the change-password flow instead of returning200. CallPOST /iam/change-passwordbefore retrying login.
Show optional properties
{
"user_name": "string",
"password": "string",
"user_type": "string"
}
{
"user_name": "admin",
"password": "********",
"user_type": "LOCAL_USER"
}
The user name to authenticate. For LDAP users, this may need to include the domain, depending on how the identity source is configured.
The password for user_name. Not returned in any response.
Identifies whether an identity is a local Installer account, a remote user authenticated through a configured LDAP identity source, or a remote LDAP group.
Login succeeded. The session cookie and XSRF token are returned in the response headers.
{
"user_name": "admin",
"display_name": "Administrator",
"user_type": "LOCAL_USER",
"roles": [
{
"role": "ENTERPRISE_ADMIN",
"display_name": "Enterprise Admin"
}
]
}
The user name that was authenticated.
The human-readable name for this user, suitable for showing in a UI.
Identifies whether an identity is a local Installer account, a remote user authenticated through a configured LDAP identity source, or a remote LDAP group.
The roles held by this user, which determine which Installer APIs the current session is authorized to call.
Response Headers
Session cookie. Send it back in the `Cookie` header of subsequent requests.
XSRF token. Send it back in the `X-XSRF-TOKEN` header of subsequent requests.
The user's password has expired. Redirects to the change-password flow instead of completing login.
Response Headers
URL of the change-password page to redirect the user to.
The request body is malformed or missing a required field.
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
The user name, password, or user type is incorrect.
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Forbidden
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Failed
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Precondition Required
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Too Many Requests
{
"error_code": 0,
"module_name": "string",
"error_message": "string"
}
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
Internal server error
"Error Object"
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
4XX and 5XX type errors with appropriate message
"Error Object"
HTTP Status or Application error code.
Module where the error happened.
Message describing the error.
curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"user_name":"string","password":"string","user_type":"string"}' https://{api_host}/sspi/iam/login