Introduction
This article will explain what it means when you attempt to log in to the application and receive the following error message:
“Authentication succeeded, but a MediaPulse User ID is not associated with ID 'XXXXXXX'.”
We’ll explore the possible reasons for this issue and provide guidance on how to resolve it.
Authentication Succeeded but User ID not associated
What does it mean when I try to log in to the application and I receive the following error:
"Authentication succeeded, but a MediaPulse User ID is not associated with ID 'XXXXXXX'" ?
The primary authentication methods for accessing the application are OpenID and Database authentication.
- Database users are solely used for the purpose of smart client access not Web access.
- OpenID users are solely used for the purpose of Web access not smart client access.
After the creation of these users on the backend, they must be linked in the application in order for the system to correctly authenticate and provide access. In the application, the User document under the System module is where this linkage is done.
OpenID Authentication
OpenID users are linked in the application via the Ext Auth Key field on the User page.
If Xytech is hosting your users, this field must be populated by either the the Object ID (the value seen in the error message) or by the User Principal Name (UPN) which is usually the hosted email address that is created inside our tenant. Please note that you cannot have a mix of Object ID and UPN, the setup is one or the other. If you're have admin access you can see what your set up is via System > Setup > OpenID Mapping. If you see the above error message, it is likely that the User document is missing the Ext Auth Key or it has been entered incorrectly. Please contact Xytech Support to ensure this setup has been done correctly. Please use 'Submit a ticket' option at the bottom of this article.
If you are using a tenant that is not hosted by Xytech, please confirm the Ext Auth Key has been correctly against the user and linked inside your Active Directory setup.
Database Authentication (SQL)
Database users are solely used for the purpose of smart client access not Web access. Database users must be linked in the application via the User ID or Long User ID fields on the User page. Once a database user has been created on the backend (SQL), the username must match the value. By default, the User ID is limited to 10 characters. If the SQL username exceeds this value, you must utilize the Long User ID field which the system can also recognize when authenticating.
If Xytech is hosting the application, Please contact Xytech Support to ensure the database user has been created and linked correctly. Please use 'Submit a ticket' option at the bottom of this article.
If you are hosting the application on-premises and are seeing the error message above when logging in with a database user, please ensure the user has been created in your database and has been correctly linked on the User page.
If you're having trouble finding the information you need, feel free to reach out to our support team by using the Submit a Ticket option below.