This API scope covers all operations related to user authentication, single sign-on (SSO), multi-factor authentication (MFA), Windows authentication, token management, and authorization checks within the MFT system.
The base endpoint URL for all operations in this scope is http://localhost:8010/vault_rest.
Authentication Requirements: Most endpoints in this scope require authentication.
- Basic Authentication: Used for initial login/authentication endpoints (e.g.,
/vault_rest/authenticate). Provide username and password in theAuthorizationheader using Basic scheme. - Bearer Token Authentication: Used for all other authenticated endpoints.
After successful authentication, an API key (token) is issued. This token must be
included in the
Authorizationheader of subsequent requests using the Bearer scheme (e.g.,Authorization: Bearer <your_api_key>).
Usage Notes:
- The
/vault_rest/authenticateendpoint is typically used to obtain an initial API key. - Token management endpoints allow for extending, creating, deleting, and recycling API keys.
- SSO and MFA endpoints provide mechanisms for integrating with external identity providers and enforcing multi-factor authentication policies.
- The
/vault_rest/authenticate-windowsendpoint facilitates Windows-integrated authentication, leveraging existing Windows session credentials.
Bearer token obtained after successful authentication.
Example: Authorization: Bearer <your_api_key>
Basic authentication using username and password.
Example: Authorization: Basic <base64_encoded_username:password>
Authentication
Endpoints for user login, logout, and general authentication processes.
Request an API Key
Authenticates a user and requests a new API key (token). This endpoint typically requires Basic Authentication (username and password) in the Authorization header. Upon successful authentication, a bearer token is returned, which should be used for subsequent API calls.
Since ## 3.11.1
Authentication successful, API key returned.
Log Out and Invalidate API Key
Logs out the current user by invalidating their active API key (token). This action effectively ends the current session.
Since ## 3.11.1
API key invalidated successfully.
Sso
Endpoints for Single Sign-On (SSO) integration and authentication flows.
Initiate SSO Pre-authentication
Initiates the Single Sign-On (SSO) pre-authentication process. This endpoint is typically the first step in an SSO flow, preparing the system for an external identity provider redirect.
Since ## 3.11.1
SSO pre-authentication initiated successfully.
Complete SSO Authentication (GET)
Completes the Single Sign-On (SSO) authentication process using a GET request,
typically after a redirect from an identity provider. The code and state
parameters are crucial for validating the authentication flow.
Since ## 3.11.1
SSO authentication completed successfully.
Complete SSO Authentication (POST)
Completes the Single Sign-On (SSO) authentication process using a POST request. This endpoint is typically used by the SSO provider to send authentication data back to the MFT system.
Since ## 3.11.1
SSO authentication content from the identity provider.
SSO authentication completed successfully.
Authenticate with SSO Token
Authenticates a user using an existing SSO token. This endpoint is used to validate and potentially refresh an SSO session.
Since ## 3.11.1
SSO token authentication successful.
Mfa
Endpoints for Multi-Factor Authentication (MFA) management and validation.
Validate One-Time Password (OTP)
Validates a One-Time Password (OTP) provided by the user, typically as part of a Multi-Factor Authentication (MFA) flow. The request body should contain the OTP.
Since ## 3.11.1
OTP validation request body.
OTP validated successfully.
Get MFA Settings
Retrieves the current Multi-Factor Authentication (MFA) settings for the system.
Since ## 3.11.1
MFA settings retrieved successfully.
Update MFA Settings
Updates the Multi-Factor Authentication (MFA) settings for the system or a specific user. The request body contains the new MFA configuration.
Since ## 3.11.1
MFA settings update request body.
MFA settings updated successfully.
Tokens
Endpoints for managing authentication tokens, including creation, extension, and deletion.
Initiate Token Exchange Pre-check
Initiates a pre-check for token exchange, often used in scenarios involving MFA or other conditional token issuance. This step might return information needed for the subsequent token exchange.
Since ## 3.11.1
Pre-exchange token request body.
Token exchange pre-check successful.
Exchange Token
Exchanges a pre-authentication token or other credentials for a full API key. This is typically the final step in a multi-stage authentication process, such as after MFA validation.
Since ## 3.11.1
Token exchange request body.
Token exchange successful, new API key issued.
Extend Authentication Token
Extends the expiration time of an existing authentication token. This allows users to maintain their session without re-authenticating.
Since ## 3.11.1
Request body for extending the token.
Token extended successfully.
Create Authentication Token
Creates a new authentication token. This endpoint might be used for generating API keys for programmatic access or for specific session types.
Since ## 3.11.1
Request body for creating a new token.
New token created successfully.
Delete Authentication Token
Deletes a specific authentication token, effectively logging out the associated session. The request body should specify which token to delete.
Since ## 3.11.1
Request body for deleting the token.
Token deleted successfully.
Extend Idle Session
Extends the idle timeout for the current user session. This is typically called periodically by the client to keep the session alive.
Since ## 3.11.1
Idle session extended successfully.
Generate a New Authentication Token
Generates a new, unique authentication token. This is often used for creating API keys for specific purposes or integrations.
Since ## 3.11.1
New authentication token generated.
Enumerate Authentication Tokens
Retrieves a paginated list of authentication tokens. This endpoint allows administrators to view and manage active tokens.
Since ## 3.11.1
List of authentication tokens retrieved successfully.
Recycle Authentication Token
Recycles the current authentication token, issuing a new one while invalidating the old one. This can be used to refresh a token's validity or to mitigate potential token compromise.
Since ## 3.11.1
Token recycled successfully, new token issued.
Authorization
Endpoints for checking user authorization against specific resources.
Check Resource Authorization
Checks if the current user is authorized to access a specific resource type. This endpoint is used to enforce fine-grained access control.
Since ## 3.11.1
Authorization check result.
Windows Authentication
Endpoints for Windows Integrated Authentication.
Authenticate with Windows Credentials
Initiates authentication using Windows credentials via negotiation-based authentication.
This endpoint leverages the existing Windows session of the client. The [Authorize]
attribute indicates that the request is expected to carry authentication information,
typically handled by the browser/server for Windows Integrated Authentication.
Upon successful negotiation, an MFT API token is issued.
Since ## 3.11.1
Windows authentication successful, API key returned.
