<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
0D51Y00006LxHx4SAFOkta Classic EngineSingle Sign-OnAnswered2019-09-17T16:06:45.000Z2019-06-19T07:28:41.000Z2019-06-20T20:04:57.000Z

Securing API with SAML

So we have, what I imagine is a very common architecture. We have a static SPA, hosted on s3/cloudfront, that talks to an api. The SPA is secured via OIDC, and it sends the JWT to the API on every request. The API verified the token, figures out who the user is, etc.

 

Now we're being required to use SAML via okta. What changes will we have to make to our architecture? I imagine we can no longer use an SPA hosted on a SPA, but would need our own server that "speaks" SAML. How do get the authenticate the API? Is there a similar concept of sending some over in a header to be verified?


  • Hi Avi,

    Related to your inquiry , we will need more information on how your system is set up , in order to investigate what would be the best way of approaching this.

     

    I would highly recommend opening a support ticket as a delicate configuration such as yours may need certain settings implemented to accommodate the desired flow .

     

     

     

     

     

    Thank you

    Andrei Kosa

    Okta Support.

    Expand Post

Loading
Securing API with SAML
Okta Support Agent (Beta)

Terms of Service

Hello! I'm the Okta Support Agent (Beta), your go-to resource for questions about Okta products. Please remember for your security and privacy, do not share any Personally Identifiable Information (PII) such as passwords, IP addresses, or other details with me.

Okta Privacy Policy and Terms of Service apply