Last update:
Last verified version: AMC 3.2.1
Issue
LDAP is configured in ASGARD without errors, but logging in with the test user fails. ASGARD reports incorrect login data.
Solution
This ASGARD behavior results from the user's LDAP group membership in various ASGARD roles.
Please make sure, that the LDAP group is only used once when assigning roles.
Related Content
- Recreating the TLS Certificate on ASGARD Analysis Cockpit
- THOR in Lab-Mode does not scan network or external drives
- THOR Scan Error: No rules with DEEPSCAN tag found
- Troubleshooting Cockpit Login Error and MySQL Connection Issues
- GRPC Connectivity Issues: Understanding TLS Inspection Errors and Solutions