@omnibase/core-js 0.9.4 → 0.9.7

package/src/apis/V1AuthApi.ts

@@ -0,0 +1,261 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Omnibase REST API
+ * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
+ *
+ * The version of the OpenAPI document: 0.9.7
+ * Contact: support@omnibase.dev
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+
+
+import * as runtime from '../runtime';
+import type {
+  GetActiveTenant200Response,
+  GetIdentity200Response,
+  GetSession200Response,
+  HandlersInternalServerErrorResponse,
+  HandlersUnauthorizedResponse,
+  ListTenants200Response,
+  Logout200Response,
+  WhoAmI200Response,
+} from '../models/index';
+import {
+    GetActiveTenant200ResponseFromJSON,
+    GetActiveTenant200ResponseToJSON,
+    GetIdentity200ResponseFromJSON,
+    GetIdentity200ResponseToJSON,
+    GetSession200ResponseFromJSON,
+    GetSession200ResponseToJSON,
+    HandlersInternalServerErrorResponseFromJSON,
+    HandlersInternalServerErrorResponseToJSON,
+    HandlersUnauthorizedResponseFromJSON,
+    HandlersUnauthorizedResponseToJSON,
+    ListTenants200ResponseFromJSON,
+    ListTenants200ResponseToJSON,
+    Logout200ResponseFromJSON,
+    Logout200ResponseToJSON,
+    WhoAmI200ResponseFromJSON,
+    WhoAmI200ResponseToJSON,
+} from '../models/index';
+
+/**
+ * 
+ */
+export class V1AuthApi extends runtime.BaseAPI {
+
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    async getActiveTenantRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetActiveTenant200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/active-tenant`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => GetActiveTenant200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Returns the full tenant object for the user\'s currently active tenant.  ## Tenant Context Users can be members of multiple tenants but only one is active at a time. The active tenant determines which resources and data the user can access.  ## Use Case Determine which tenant context to use for API calls and data filtering.
+     * Get active tenant
+     */
+    async getActiveTenant(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetActiveTenant200Response> {
+        const response = await this.getActiveTenantRaw(initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    async getIdentityRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetIdentity200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/identity`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => GetIdentity200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Returns the current authenticated user\'s identity information (traits like email, name).  ## Identity Data - User ID (unique identifier) - Traits (email, first name, last name based on identity schema) - Schema ID - Created/updated timestamps  ## Use Case Lighter alternative to full session when you only need user profile data.
+     * Get current identity
+     */
+    async getIdentity(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetIdentity200Response> {
+        const response = await this.getIdentityRaw(initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    async getSessionRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<GetSession200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/session`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => GetSession200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Returns the current authenticated user\'s session including identity and tenant information.  ## Session Data - Session metadata (ID, expiry, authentication methods) - Identity information (user ID, traits like email, name) - Active tenant context (if user has tenant membership)  ## Authentication Requires valid session via Cookie or X-Session-Token header.
+     * Get current session
+     */
+    async getSession(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<GetSession200Response> {
+        const response = await this.getSessionRaw(initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
+     */
+    async listTenantsRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ListTenants200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/tenants`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => ListTenants200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Returns all tenants the user is a member of with their active status.  ## Tenant Memberships Users can be members of multiple tenants. Each membership has: - Active status (only one tenant can be active at a time) - Full tenant information (ID, name, type, etc.)  ## Use Case Display tenant switcher UI or list all organizations the user belongs to.
+     * List user\'s tenants
+     */
+    async listTenants(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ListTenants200Response> {
+        const response = await this.listTenantsRaw(initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    async logoutRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<Logout200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/logout`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'POST',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => Logout200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Creates a Kratos logout flow and returns the logout URL for browser redirect.  ## Logout Process 1. Request this endpoint to get logout URL 2. Redirect browser to the returned logout_url 3. Session will be invalidated and user logged out  ## Cookie Cleanup The logout URL handles clearing session cookies automatically.
+     * Logout user
+     */
+    async logout(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Logout200Response> {
+        const response = await this.logoutRaw(initOverrides);
+        return await response.value();
+    }
+
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    async whoAmIRaw(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<WhoAmI200Response>> {
+        const queryParameters: any = {};
+
+        const headerParameters: runtime.HTTPHeaders = {};
+
+        if (this.configuration && this.configuration.apiKey) {
+            headerParameters["Cookie"] = await this.configuration.apiKey("Cookie"); // SessionAuth authentication
+        }
+
+
+        let urlPath = `/api/v1/auth/whoami`;
+
+        const response = await this.request({
+            path: urlPath,
+            method: 'GET',
+            headers: headerParameters,
+            query: queryParameters,
+        }, initOverrides);
+
+        return new runtime.JSONApiResponse(response, (jsonValue) => WhoAmI200ResponseFromJSON(jsonValue));
+    }
+
+    /**
+     * Lightweight endpoint to check if the user is authenticated.  ## Response Returns boolean authentication status and user ID if authenticated.  ## Use Case Quick auth checks for route guards without fetching full session data.
+     * Check authentication status
+     */
+    async whoAmI(initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<WhoAmI200Response> {
+        const response = await this.whoAmIRaw(initOverrides);
+        return await response.value();
+    }
+
+}

package/src/apis/V1DatabaseApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/V1PaymentsApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/V1PermissionsApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/V1StorageApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/V1StripeApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/V1TenantsApi.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/apis/index.ts

@@ -1,5 +1,6 @@
 /* tslint:disable */
 /* eslint-disable */
+export * from './V1AuthApi';
 export * from './V1DatabaseApi';
 export * from './V1PaymentsApi';
 export * from './V1PermissionsApi';

package/src/models/AcceptInvite200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ApiV1StorageDownloadPost200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ApiV1StorageObjectDelete200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ApiV1StorageUploadPost200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ArchiveAllStripeConfig200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/AssignRole200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/CheckPermission200Response.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.4
+ * The version of the OpenAPI document: 0.9.7
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/src/models/ClientAuthenticatorAssuranceLevel.ts

@@ -0,0 +1,55 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * Omnibase REST API
+ * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
+ *
+ * The version of the OpenAPI document: 0.9.7
+ * Contact: support@omnibase.dev
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+
+
+/**
+ * 
+ * @export
+ */
+export const ClientAuthenticatorAssuranceLevel = {
+    AUTHENTICATORASSURANCELEVEL_AAL0: 'aal0',
+    AUTHENTICATORASSURANCELEVEL_AAL1: 'aal1',
+    AUTHENTICATORASSURANCELEVEL_AAL2: 'aal2',
+    AUTHENTICATORASSURANCELEVEL_AAL3: 'aal3'
+} as const;
+export type ClientAuthenticatorAssuranceLevel = typeof ClientAuthenticatorAssuranceLevel[keyof typeof ClientAuthenticatorAssuranceLevel];
+
+
+export function instanceOfClientAuthenticatorAssuranceLevel(value: any): boolean {
+    for (const key in ClientAuthenticatorAssuranceLevel) {
+        if (Object.prototype.hasOwnProperty.call(ClientAuthenticatorAssuranceLevel, key)) {
+            if (ClientAuthenticatorAssuranceLevel[key as keyof typeof ClientAuthenticatorAssuranceLevel] === value) {
+                return true;
+            }
+        }
+    }
+    return false;
+}
+
+export function ClientAuthenticatorAssuranceLevelFromJSON(json: any): ClientAuthenticatorAssuranceLevel {
+    return ClientAuthenticatorAssuranceLevelFromJSONTyped(json, false);
+}
+
+export function ClientAuthenticatorAssuranceLevelFromJSONTyped(json: any, ignoreDiscriminator: boolean): ClientAuthenticatorAssuranceLevel {
+    return json as ClientAuthenticatorAssuranceLevel;
+}
+
+export function ClientAuthenticatorAssuranceLevelToJSON(value?: ClientAuthenticatorAssuranceLevel | null): any {
+    return value as any;
+}
+
+export function ClientAuthenticatorAssuranceLevelToJSONTyped(value: any, ignoreDiscriminator: boolean): ClientAuthenticatorAssuranceLevel {
+    return value as ClientAuthenticatorAssuranceLevel;
+}
+