This API scope covers all endpoints related to user authentication, Single Sign-On (SSO), Multi-Factor Authentication (MFA), Windows Integrated Authentication, token management, and authorization checks within the MFT system.
The base endpoint URL for all operations is http://localhost:8010/vault_rest.
Most authenticated endpoints require an API key (bearer token) provided in the Authorization: Bearer <token> header. This token can be obtained from the /vault_rest/authenticate endpoint using basic authentication (username and password) or through SSO/Windows authentication flows.
For initial authentication endpoints like /vault_rest/authenticate, basic authentication (Authorization: Basic <base64(username:password)>) is required.
API keys have an expiration time and can be extended or recycled using the token management endpoints.
Basic authentication using username and password.
Bearer token authentication using an API key.
Authentication
Endpoints for user login, logout, and session management.
Request an API key
Requests an API key (authentication token) for subsequent API calls. This endpoint typically requires basic authentication (username and password) in the Authorization header to obtain a bearer token.
API key successfully generated.
Log out and invalidate the current API key
Invalidates the current authentication token (API key), effectively logging out the user. The token can no longer be used for subsequent authenticated requests.
Authentication token successfully invalidated.
Sso
Endpoints for Single Sign-On (SSO) authentication flows.
Initiate SSO pre-authentication
Initiates the pre-authentication process for Single Sign-On (SSO) using OIDC. This endpoint typically returns information needed to redirect the user to the identity provider.
SSO pre-authentication initiated successfully.
Complete SSO authentication via GET
Completes the Single Sign-On (SSO) authentication process by receiving an authorization code and state via a GET request. This is commonly used as a redirect URI callback from an identity provider after successful authentication.
SSO authentication completed successfully.
Complete SSO authentication via POST
Completes the Single Sign-On (SSO) authentication process by receiving authentication data via a POST request. This is typically used for callback mechanisms from an identity provider.
SSO authentication details.
SSO authentication completed successfully.
Authenticate using an SSO token
Authenticates a user using an existing Single Sign-On (SSO) token. This endpoint validates the provided SSO token to establish an authenticated session.
SSO token authenticated successfully.
Mfa
Endpoints for Multi-Factor Authentication (MFA) configuration and validation.
Validate a One-Time Password (OTP)
Validates a provided One-Time Password (OTP) as part of a multi-factor authentication (MFA) flow. This is typically called after initial authentication to complete the login process.
OTP validation request.
OTP validated successfully.
Get Multi-Factor Authentication (MFA) settings
Retrieves the current Multi-Factor Authentication (MFA) settings for the current user or system.
MFA settings retrieved successfully.
Update Multi-Factor Authentication (MFA) settings
Updates the Multi-Factor Authentication (MFA) settings for the current user or system. This can include enabling/disabling MFA, configuring methods, etc.
MFA settings update request.
MFA settings updated successfully.
Tokens
Endpoints for managing API keys (authentication tokens), including creation, extension, and revocation.
Initiate token exchange for MFA
Initiates the process to exchange an existing authentication token for a new one, typically in scenarios involving Multi-Factor Authentication (MFA) where an OTP is required for the exchange.
Token exchange pre-initiated successfully.
Complete token exchange with OTP
Completes the token exchange process by providing the necessary information, including an OTP, to receive a new authentication token. This is part of an MFA-enabled token refresh or upgrade flow.
Token exchange request with OTP.
Token exchange completed successfully.
Extend the expiration of an authentication token
Extends the expiration time of an existing authentication token. This allows users to maintain their session without needing to re-authenticate fully.
Request to extend token expiration.
Token expiration extended successfully.
Create a new authentication token
Creates a new authentication token. This endpoint can be used by administrators or authorized users to generate tokens for other users or service accounts.
Request to create a new authentication token.
New authentication token created successfully.
Delete a specific authentication token
Deletes a specific authentication token, rendering it invalid for future API requests. This can be used to revoke access for a particular token.
Request to delete an authentication token.
Authentication token deleted successfully.
Extend the idle session timeout
Extends the idle session timeout for the current authenticated session. This prevents the session from expiring due to inactivity.
Idle session timeout extended successfully.
Generate a new API key
Generates a new API key (authentication token) for the current authenticated user. This can be used to replace an existing token or generate an additional one.
New API key generated successfully.
Enumerate authentication tokens
Retrieves a paginated list of authentication tokens. This endpoint is typically used by administrators to manage and monitor active tokens.
List of authentication tokens retrieved successfully.
Recycle the current authentication token
Recycles the current authentication token, effectively invalidating it and generating a new one in its place. This is useful for rotating tokens without a full logout/login cycle.
Authentication token recycled successfully.
Authorization
Endpoints for checking user permissions against specific resources.
Check authorization for a specific resource type
Checks if the current authenticated user has authorization to access or perform actions on a specified resource type. The resourceType parameter identifies the type of resource being checked.
Authorization check result.
Windows Authentication
Endpoints for authenticating users via Windows Integrated Authentication.
Authenticate using Windows Integrated Authentication
Authenticates a user based on their Windows Integrated Authentication (WIA) identity. This endpoint leverages the existing Windows authentication context to generate an API key (authentication token) for the user. The X-Forwarded-For header is used to determine the client IP address if present.
This endpoint does not require an explicit Authorization header in the API request, as Windows authentication occurs at the HTTP transport layer.
Windows authentication successful, API key generated.
Service unavailable or user could not be uniquely identified.
