Applications Configuration
Applications in AuthAction represent your client apps (web, mobile, or backend services) that use AuthAction for authentication. This guide covers creating applications and configuring their settings.
Application Types
Section titled “Application Types”| Type | Description | Use Case |
|---|---|---|
| Single Page Application (SPA) | Public client for web apps | React, Angular, Vue, Next.js, or other frontend frameworks |
| Machine-to-Machine (M2M) | Confidential client for backend services | APIs, scripts, server-side integrations |
Creating an Application
Section titled “Creating an Application”- Log in to the AuthAction Dashboard.
- Select your tenant.
- Navigate to Applications in the sidebar.
- Click Create Application.
- Enter a name and select the application type (SPA or M2M).
- Save the application.
Configuring Callback URLs (SPA)
Section titled “Configuring Callback URLs (SPA)”For SPA applications, configure the following:
- Redirect URI: Where users are sent after login (e.g.
http://localhost:3000/callbackorhttps://myapp.com/callback). - Logout Redirect URI: Where users are sent after logout (e.g.
http://localhost:3000orhttps://myapp.com).
The redirect URI must exactly match the URL used in your authorization request. Wildcards may be supported depending on your tenant configuration.
Granting API Access (M2M)
Section titled “Granting API Access (M2M)”For M2M applications that call the Management API or other APIs:
- Open the application settings.
- Go to the API Server or APIs tab.
- Enable access to the required API resources (e.g. AuthAction Management API).
- Save the changes.
Enabling Connections
Section titled “Enabling Connections”Link your application to the authentication methods you want to support:
- Database Connection: Enable the database connection for email/password or passkey sign-in.
- Social Connections: Enable Google, GitHub, and other providers as needed.
Related
Section titled “Related”- Database Connections: Set up authentication methods.
- Social Connections: Add social login providers.
- API Servers: Configure API resources for audience validation.