Forum Discussion
southern_shredd
Cirrus
CirrusEncryption error - SAML assertion: response is not encrypted
We are trying to configure out APM with Azure SAML authentication. After login on and succedded we can an error and the logs show the following: modules/Authentication/Saml/SamlSPAgent.cpp: 'verif...
AlexBCT
Cumulonimbus
CumulonimbusHi,
From the log messages, I assume you have configured the F5 as the SAML SP?
If so, can you have a look under the SAML SP Service configuration (Access ›› Federation : SAML Service Provider : Local SP Services), under the Security Settings tab and see if the flag "Want Encrypted Assertion" is checked? If so, uncheck it.
SAML encryption is a way of ensuring that the client cannot read the SAML request, but it has no real impact on the integrity of the message, this is where "Want Signed Assertion" is for. "Want Signed Assertion" should always be checked, "Want Encrypted Assertion" is an optional extra and is often (and by default) unchecked.
Hope this helps.
southern_shreddThanks that seems to have resolved that error. The login is now successfull both on Azure and on APM how we seem to another error when we receive the successfull token
The error seem to be wiht the replyURL being incorrect? Wich URL should we configure for this and in which format?
We have tried the Entity ID URL, we have tried the initial hostname URL but still get an error
1): our.website.com/saml/sp/profile/post/acs
2): entityid url
AADSTS50011: The reply URL 'https://login.microsoftonline.com/ourappliaction' specified in the request does not match the reply URLs configured for the application 'https://login.microsoftonline.com/azureentityid/saml2'- AlexBCT
Nice! one error down, let's see how many there are left to go... 😉 Sounds like you're close though.
Purely going on ReplyURL, you should have the following: https://app.example.com/saml/sp/profile/post/acs
...but there may be more to this as that will depend a bit on both the AzureAD configuration as well as the APM configuration. Now that you've resolved the issue with the encryption, it may be a good idea to create a new metadata file on the F5 and re-import it in to AzureAD. This way, you'll let the F5 decide which information should be imported where in the AzureAD SAML config.