# Do we have the latest, maintained Okta SAML SSO sample I can examine?

**URL:** <https://devforum.okta.com/t/do-we-have-the-latest-maintained-okta-saml-sso-sample-i-can-examine/27336>\
**Category:** Questions\
**Created:** [March 19, 2024, 5:06pm UTC](https://devforum.okta.com/t/do-we-have-the-latest-maintained-okta-saml-sso-sample-i-can-examine/27336 "2024-03-19T17:06:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tlee](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@tlee](https://devforum.okta.com/u/tlee)\
**Post date:** [March 19, 2024, 5:06pm UTC](https://devforum.okta.com/t/do-we-have-the-latest-maintained-okta-saml-sso-sample-i-can-examine/27336/1 "2024-03-19T17:06:03Z")

</div>

The current Github project, [GitHub - oktadev/okta-spring-boot-saml-example: Spring Boot, SAML, and Okta](https://github.com/oktadev/okta-spring-boot-saml-example) , was originally maintained by Matt Raible, who now no longer works at Okta.

There is an issue with the project sample’s code, where it couldn’t handle Okta’s initial OPTIONS request before proceeding with the actual POST SAML request. I reported this issue on the project, but because the project is now stale, I closed the issue.

What’s the proper way of handling the Okta’s OPTIONS request? Do we ignore it, and keep seeing the “No relying party registration” error? Or is there a better way of fixing the problem?

---

<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:** [April 18, 2024, 5:06pm UTC](https://devforum.okta.com/t/do-we-have-the-latest-maintained-okta-saml-sso-sample-i-can-examine/27336/2 "2024-04-18T17:06:37Z")

</div>

Closed on April 18, 2024, 5:06pm UTC

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