MNPR authentication fails during login in Adobe Experience Manager
In Adobe Experience Manager, MNPR users are unable to log in through the MNPR login page because authentication fails before password validation and group validation occurs. The issue affects users who appear in the user management interface but still fail authentication. To fix this issue, restore the required user profile attributes and recreate affected user profiles by using the standard user management interface in Adobe Experience Manager.
Description description
Environment
Adobe Experience Manager (all versions)
Symptoms
- MNPR users are unable to log in through the MNPR login page.
- Authentication attempts fail before password validation.
- Group validation (such as mnpr_user or mnpr_admin) is not reached.
- The user appears in the user management interface, but authentication fails.
Cause
The application cannot map the provided loginId to a userId. This is typically caused by incomplete or improperly created user profiles, often resulting from manual modifications of user nodes rather than using the standard user management interface. As a result, required profile attributes for authentication may be missing or outdated.
Resolution resolution
Follow the steps below to resolve the issue.
-
Create users using the standard AEM user management interface (
security/users.html).Note: Do not manually create or modify user nodes in CRXDE or through Package Manager, as this can lead to incomplete user profiles.
-
Verify user profile attributes:
- In the user management interface, confirm that each user has all mandatory attributes required for authentication, such as
loginId,userId, and the correct group memberships (for example,mnpr_userandmnpr_admin). - Add users to the appropriate groups using the interface instead of editing nodes directly.
- In the user management interface, confirm that each user has all mandatory attributes required for authentication, such as
-
Review custom authentication logic. If your application uses custom logic to map
loginIdtouserId, confirm that it functions correctly and does not rely on outdated or manually edited user nodes. -
Test the authentication flow:
- Attempt to log in with the affected user accounts after verifying and correcting user profiles.
- Check authentication logs to confirm that the mapping and authentication are successful.
Notes
- For AEM as a Cloud Service (AEMaaCS), do not manually edit user nodes through CRXDE, as this is not supported. Always use the user management interface for user administration.
- Avoid manual node modifications. Do not use CRXDE or Package Manager to edit user nodes as a workaround, as this can cause further inconsistencies and affect AEM services.