Whitelisting Okta for Third-Party Cookies

All apps that can be configured using SAMLAn acronym for Security Assertion Markup Language, SAML is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). The SAML standard addresses issues unique to the single sign-on (SSO) solution, and defines three roles: the end user, the IdP, and the SP. Here's how SAML works through Okta: SP-initiated flow: the end user requests (principally through a browser) a service from the SP. The SP requests and obtains an identity assertion from the IdP (in this case, Okta). On the basis of this assertion, the SP can decide whether or not to authorize or authenticate the service for the end user. IdP-initiated flow: with Okta as the IdP, an end user goes to the Okta browser and clicks on an app, sending a SAMLResponse to the configured SP. A session is established with the SP, and the end user is authenticated. have inline instructions that guide you through the configuration. If you have blocked third-party cookies on your site, these instructions are prevented from appearing correctly.

Ensure that your Okta orgThe Okta container that represents a real-world organization. URL is whitelisted for your browser. From your browser’s page for setting third-party cookies, use the following URL to add Okta as a whitelisted option, as shown as an example in Chrome below.