# Okta SAML Signature Validation - now working

**URL:** <https://devforum.okta.com/t/okta-saml-signature-validation-now-working/30535>\
**Category:** SAML\
**Tags:** spring\
**Created:** [September 12, 2024, 4:15pm UTC](https://devforum.okta.com/t/okta-saml-signature-validation-now-working/30535 "2024-09-12T16:15:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jridge](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@jridge](https://devforum.okta.com/u/jridge)\
**Post date:** [September 12, 2024, 4:15pm UTC](https://devforum.okta.com/t/okta-saml-signature-validation-now-working/30535/1 "2024-09-12T16:15:54Z")

</div>

After a significant amount of effort we finally managed to successfully enable the Okta SAML “Signed Requests” flag. It turned out that for us the problem was somewhat related to the example SAML client we used to act as the SP-Initiated SAML client. That client isn’t properly configured to provide the desired “NameID Format” as part of the SAML AuthnRequest. We resolved this by iteratively working with the actual 3rd party client and referring to the following URL which provided the missing solution: [Okta SAML Integration with Signed Requests - Auth0 Community](https://community.auth0.com/t/okta-saml-integration-with-signed-requests/106702)

For us the gist of the problem was:  
We were missing the “Name ID Format” setting within the SAML AuthnRequest.

I mention this for 2 reasons.

a) Helping out the many others experiencing this same issue (often without finding a solution).

b) I’d like suggestions on an easy approach to fixing the original example Spring Boot client we initially worked with. See: [https://www.baeldung.com/spring-security-saml](https://www.baeldung.com/spring-security-saml)

For question b) please provide suggestions how to easily modify the Spring Boot example to provide the missing item from the SAML AuthnRequest:  
\<samlp:NameIDPolicy Format=“urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified” /\>

TIA for any valid suggestion.

---

<div class="post-metadata">

**Author:** ![vk-giri](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/vk-giri/32/5178_2.png) [@vk-giri](https://devforum.okta.com/u/vk-giri)\
**Post date:** [September 27, 2024, 6:10am UTC](https://devforum.okta.com/t/okta-saml-signature-validation-now-working/30535/2 "2024-09-27T06:10:26Z")

</div>

HI,

I empathize with your situation, but unfortunately, we can’t provide official recommendations for fixing third-party SDKs. Since the sample [https://www.baeldung.com/spring-security-saml](https://www.baeldung.com/spring-security-saml) you linked to is not from Okta, I suggest getting in touch with the original author for help.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [October 27, 2024, 6:10am UTC](https://devforum.okta.com/t/okta-saml-signature-validation-now-working/30535/3 "2024-10-27T06:10:46Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.