Jira, Confluence, and Bitbucket offer “anonymous users” to view public content without having an authenticated session.
In adddition Kantega SSO Enterprise provides the ability to require users to authenticate with their identity provider, using SSO, to access anonymous content in Jira and Confluence. This enables your organization to save on license costs while maintaining secure access to all your content.
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.
The Group Memberships settings allow configuring conditions for when the user is created. This can be configured fluently with Authenticated Anonymous Access. For example, you can configure a policy in which users and group memberships are created automatically for all users logging in and belonging to the editor group in your identity provider. In contrast, all other users will fall back to “anonymous access” after logging in with SSO.