Configuring Login and Authentication
Adeptia Automate uses a gateway layer to protect all platform resources, ensuring that only authenticated users and sessions can access integration services, monitoring tools, and administrative functions. This page explains how authentication works conceptually and what you need to configure to enable secure login for your deployment.
Authentication Architecture
All access to the Adeptia Portal and APIs flows through the gateway layer. The gateway evaluates every request for a valid session before forwarding it to the underlying platform services. This means:
- Unauthenticated requests are rejected at the gateway before reaching any integration logic.
- Session tokens are validated on every request; there is no implicit trust once authenticated.
- Authentication failures are logged for audit purposes.
Supported Authentication Methods
Adeptia supports the following authentication methods:
| Method | Description |
|---|---|
| Local authentication | Username and password stored in the Adeptia user directory |
| LDAP / Active Directory | Federate authentication to your organization's directory service |
| SAML 2.0 (SSO) | Single sign-on via a SAML identity provider (IdP) |
Configuring Local Authentication
Local authentication is enabled by default. User accounts are created and managed in Administrate > Users. Passwords are stored as salted hashes; plain-text passwords are never persisted.
Configuring LDAP Authentication
To connect Adeptia to an LDAP directory:
- Navigate to Administrate > Security Provider > Authentication.
- Select LDAP as the authentication type.
- Provide the LDAP server URL, bind DN, bind password, and user search base.
- Save and test the configuration.
When LDAP authentication is active, users authenticate using their directory credentials. The platform maps LDAP group membership to Adeptia roles according to the role-mapping configuration you define.
Configuring SAML SSO
For SAML-based SSO:
- Register Adeptia as a Service Provider (SP) in your identity provider. Use the Adeptia SP metadata URL to configure the trust relationship.
- In the Portal, navigate to Administrate > Security Provider > Authentication and select SAML.
- Upload your IdP's metadata XML or provide the IdP metadata URL.
- Configure attribute mappings to map SAML assertions to Adeptia user attributes (username, roles).
- Save and test with a user who has access to both the IdP and Adeptia.
Session Timeout
Sessions expire after a configurable period of inactivity. The default timeout is 30 minutes. To change the session timeout, contact your Adeptia administrator.
Related Pages
- Setting Up TLS Keystores and Certificates: TLS configuration for secure connections
- Repository and Role Map: RBAC and user role management