Submit a Ticket
Logging into CPM using Identity Provider may fail with an error "An error occurred"
When trying to log in to CPM, you may receive the following error:
In the CPM log files, there will be no related error messages, but in the Windows Event viewer you can find these errors: AD FS errors 261 and/or 364:
AD FS error 364:
AD FS error 354:
: MSIS3200: No AssertionConsumerService is configured on the relying party trust '
' that is a prefix match of the AssertionConsumerService URL '
' specified by the request.
AD FS error 261:
The request specified an Assertion Consumer Service URL '
' that is not configured
on the relying party '
Assertion Consumer Service URL:
This issue usually happens because of misconfiguration of the Relying Party Trusts in the AD FS Management console. For example, if "Trusted URL" specified not as described in the user guide.
Configure "Trusted URL" option as described in the user guide:
Try to login to the CPM again.
Updated: 12 Dec 2018 06:31 AM
Help us to make this article better
AD FS may produce “An error occurred” page when logging in or performing Test Connection
SAML Identity Provider user log in issues
CPM server may display error "Signature validation failed. SAML Response rejected"
Login to the CPM using an IDP may fail with the "Invalid issuer" error message
IDP/SAML integration may fail with "Failed getting CPM public host name"
Help Desk Software
by Zoho Desk