![]() MIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQCoLiGwr/Y1vKPq So far I tried openssl rsautl: $ cat encrypted_assertion.txtĦMFicPXJ3ycJtj3grCsaY4zxk2eEXQ3s2eCXGDCtJMMKN4PcgCCihA/jljs2jbfo/bC+xegsU74u I checked with IT and they told me to figure out how to decrypt the EncryptedAssertion using the private key via openssl or a custom Python script. I was able to decrypt a SAML response from a development stack I ran locally via but the page recommends not to upload production keys. Unfortunately the application logs the SAML response containing the EncryptedAssertion and I am unable to decrypt it locally. To provide further assistance to our customer we want to look at the Assertion in the SAML response to take a look at the problem's cause. We confirmed that our customer has configured NameID as outgoing claim in their ADFS: ![]() : NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration Unfortunately our system complains about the SAML responses: Metadata has been exchanged and the connection works. ![]() ![]() Our customer uses ADFS as identity provider. Our system supports SAML2 and acts as service provider. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |