Submit substrate front-door credentials.

POST

/v1/iam/front-login

Code sample: Shell / cURL

curl --request POST \
  --url https://stratum.example.com/v1/iam/front-login \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data email=example \
  --data password=example \
  --data mfa=example \
  --data rd=example

• A Stratum cluster endpoint.

Validates the submitted credentials against Stratum-IAM and, on success, sets the domain-wide session cookie and redirects to rd (or the install root). On failure it re-renders the login form. Only active when a front-door domain is configured.

Authorizations

• bearerAuth

Request Body^required

Media typeapplication/x-www-form-urlencoded

object

email

required

string

password

required

string

mfa

string

rd

string

Example ^generated

email=example&password=example&mfa=example&rd=example

Responses

200

Login failed; the login form is re-rendered with an inline error.

Media typetext/html

string

302

Login succeeded; session cookie set and redirected to the tool.

404

Resource not found.

Media typeapplication/problem+json

object

type

required

string format: uri

title

required

string

status

required

integer

>= 400 <= 599

detail

string

instance

string format: uri-reference

requestId

required

string

code

required

string

issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object

code

required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string

statement

required

Index of the statement at fault; -1 for the document as a whole.

integer

>= -1

detail

required

string

action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string

errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object

field

required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string

message

required

string

details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object

key

additional properties

any

Example

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}