• Airlock Secure Access Hub
  • About this document
  • About Airlock IAM
  • IAM 8.4 release notes
  • Security best practices
  • Installation and upgrade
  • Operation
  • Initial configuration
  • Configuration management
  • Authentication
  • Self-services
  • Target applications
  • OAuth and OIDC
  • SAML
    • Terms and definitions
    • SSO with POST binding
    • SSO with HTTP artifact binding
    • SAML Single Logout (SLO)
    • HTTP Proxy for artifact binding
    • Troubleshooting SAML
      • AuthnContext mismatch to RequestAuthnContext
      • Missing def. AssertionConsumerService
      • SLO exception
      • AuthnReq. for unknown app
      • Entity IDs mismatch
      • SLO not working
      • Host flag without FQDN
      • MetaAlias missing / entity IDs mismatch
      • NPE at SAML processing
      • CoT list mismatch
      • Entity ID not found
      • Unsupported SAML signature algorithms in IAM 7.6 and later
  • API access control
  • Flows (Airlock IAM concept)
  • Loginapp Configuration
  • Adminapp Configuration
  • Service Container Configuration
  • Transaction Approval Configuration
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. SAML
  2. Troubleshooting SAML
  3. Entity IDs mismatch

Entity IDs do not match

Exception (in IdP):

 
Example

Error processing LogoutResponse. LogoutRequestID and InResponseTo Do Not Match

Reason:

There is nothing wrong with the request IDs – instead, the entityID might be wrong.

Solution:

Check if the entityID in the sp*xml in the IdP and the sp*xml in the SP match.