Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

Applications in Lerian Console represent Access Manager API clients that can authenticate and interact with the platform’s services. Each application has unique credentials (Client ID and Client Secret) used for machine-to-machine (M2M) authentication. In multi-tenant deployments, the list is scoped to the tenant of the logged-in administrator. Console does not expose applications from other tenants.

Accessing the Applications page


To access the Applications section:
1
Click the gear icon () in the top navigation bar.
2
Select Applications from the sidebar.
3
The Applications page displays all registered applications in a table with the following columns:
  • Name – The application identifier
  • ClientId – The unique client identifier for authentication
  • ClientSecret – The secret key for authentication
  • Creation Date – When the application was created
  • Actions – Available operations for each application
Default applications (such as the Lerian Console application) cannot be modified or deleted. These are protected system applications required for platform functionality.

Available actions


From the Applications page, you can:

Create an application

Register a new API client with authentication credentials.

View application details

View the details and credentials of an existing application.

Delete an application

Remove an application and revoke its access.

Security considerations


Keep your credentials secure. The Client ID and Client Secret are sensitive information. Store them securely and never expose them in client-side code or public repositories.
  • Credentials are displayed in the applications table and can be copied using the copy button
  • Deleting an application immediately revokes access for all services using those credentials
  • Create separate applications for different services or environments to maintain security isolation
  • Use the Identity APIs when you need provider links, default-provider configuration, or other application settings that are not exposed in Console