---
title: "Step-up an existing JWT with additional auth"
method: PUT
path: "/eclipse-conductor/rest/v1/authentication/jwt"
tags: ["a) Authentication"]
---

# Step-up an existing JWT with additional auth

`PUT /eclipse-conductor/rest/v1/authentication/jwt`

Elevates an existing JWT by providing additional authentication data, enabling operations that require stepped-up authorisation.

## Request body

- StepUpRequest
  - `base64EncodedChallengeHash` string
  - `base64EncodedChallengeResponse` string
  - `base64EncodedSelfie` string
  - `deviceFingerprint` string
  - `identity` string
  - `intentId` string
  - `jwt` string
  - `otp` string
  - `password` string

## Response `200`

OK

- Jwt
  - `csrfHeaderName` string
  - `csrfToken` string
  - `expires` string, date-time — The date and time the JWT expires and should be refreshed before
  - `expiresEpochSecs` integer
  - `headerName` string — The HTTP header name to use in order to pass the JWT as the bearer token. E.g. Authorization
  - `headerValue` string — The HTTP header value to use in order to pass the JWT as the bearer token. E.g. Bearer AAAA...
  - `refreshToken` string
  - `roles` string[] — The roles this login is associated with
  - `sessionId` string — A unique identifier for this login session. Typiclaly not needed by the caller
  - `tenantId` integer — The tenant ID associated with these credentials. Optional as some identities are global and not associated to any specific tenant

## Other responses

- `400` — Bad Request
- `401` — Unauthorized - step-up authentication failed
- `500` — Internal Server Error

---

[API](https://skmtc.net/eftcorp/apis/eclipse-rest-api.md) · [All operations](https://skmtc.net/eftcorp/apis/eclipse-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/eftcorp/eclipse-rest-api/versions/9213d52d49a3/schema)