Atlassian’s applications Jira, Confluence, and Bitbucket offer “anonymous browsing” for users to view public pages content without having a logged in user with group rights in the host product. Kantega SSO offers an authenticated anonymous browsing, where all users have to authenticate with SSO to get access to even public pages. However, for example, users that don’t need a local user on Bitbucket, will do not have to get a user to have secure SSO-verified access to company-public pages on an instance running on the internetan authenticated session. Kantega SSO Enterprise provides the ability to require users to authenticate with your identity provider, using SSO, to access anonymous content.
This enables your organization to save licenses, since company-public pages can be browsed and viewed securely without the entire organization having to create a user on the instance.Note that the on license costs while maintaining secure access to all your content.
The SSO verification means that the users are not browsing truly anonymously since their identity is known, but get a . A session cookie in their browser that lives in is created the same way that as a normal regular login, only that they have no local user and no groups or rightsexcept that the session is not related to local user in the host product. You can also not have truly public content while this feature is enabled, as accessing any content requires users to have a session.
Configuration
The setting can be activated on in the Identity Provider settings, under USER PROVISIONING > Authenticated Anonymous Browsing.
...
Configuring related settings in Kantega SSO Enterprise
Like As shown in the yellow message box in the screenshot above, the settings under Just-in-time provisioning have an effect on settings affect how Authenticated Anonymous Browsing works since they both features are mechanisms related to the presence of user accounts. This has further implications if you configure Group Memberships, where you can configure . If Just-in-time provisioning is set to create users, this will take precedence over anonymous browsing.
The Group Memberships settings allow configuring conditions for when the user shall be is created. This can be configured fluently with Authenticated Anonymous Browsing. For example, you can configure a policy where in which users and group memberships are created automatically for all users logging in and belonging to the “Developers” editor group in your SSO Identity Provider get users and group memberships created automatically in Bitbucket, while identity provider. In contrast, all other users will fall back to browse Bitbucket “anonymously” , after logging in with SSO.
...