title: Single Sign On with Okta session
body: <p>I have multiple web applications running in different domains. Okta is the identity/auth provider for all these applications. After integrating with Okta in one of the application (following the Java example provided in Okta documentation), a new cookie (<strong>sid</strong>) is being created in Okta domain (<a href="https://developer.okta.com/docs/reference/api/sessions/" rel="nofollow noreferrer">https://developer.okta.com/docs/reference/api/sessions/</a>).</p>
  <p>How do I use this to SSO into other web application. What is the best approach to allow access to other application without prompting login credentials again?</p>
  <p>Do I need to invoke <strong>getCurrentSession</strong> API in every application and redirect to login page only if the API response is 404 (as per doc, getCurrentSession will retrieve the current active session based on the Okta cookie).</p>
  <p>Please share thoughts.</p>