Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SSO-verification means that the users are not accessing Jira or Confluence truly anonymously since their identity is known. A session cookie is created the same way as in a regular login, except that the session is not related to a local user in the host product. With this feature enabled, it's important to note that truly public content is restricted. Accessing any content now mandates users to have an active session, ensuring a more controlled and secure environment.

Configure

...

Enable SSO-Verified Anonymeos Access to allow users who do not have Jira or Confluence accounts to access JIRA/Confluence anonymously while still benefiting from the security features of Single Sign-On.

...

Configuring related settings in Kantega SSO Enterprise

As shown in the screenshot above, the Just-in-time provisioning settings affect how Authenticated Anonymous Acess works since both features are related to the presence of user accounts. If Just-in-time provisioning is set to create users, this will take precedence over anonymous access.

...