Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expand
titleShow Page Tree structure

Page Tree
root@parent
startDepth1

Jira, Confluence and Bitbucket offer anonymous users to view public content without having an authenticated session.

Enable SSO-Verified Anonymeos Anonymous Access in KSSO to allow users who do not have Jira or Confluence accounts to access JIRAJira/Confluence anonymously while still benefiting from the security features of Single Sign-On. This enables your organization to save on license costs while maintaining secure access to all your content.

...

Configure SSO-verified Anonymous Access in Kantega SSO Enterprise

Prerequisite

Anonymous access must be enabled in Jira/Confluence for this feature to work. Edit permissions in Jira/Confluence to enable

Examples, anonymous access

...

in Jira and Confluence

...

Users that require editing rights will have to be provisioned with a license group in Jira/Confluence. This way only the users needing to edit will consume a license while those not created in Jira/Confluence will be given an anonymous access session as fallback.

...

How to configure in KSSO

  1. Select Identity Providers in the KSSO menu and choose the applicable Identity Provider in the overview page, and IdP overview will open.

    Skjermbilde 2024-09-03 kl. 13.25.49.pngImage Removed

    Enable idp overview.pngImage Added

  2. Select Identity providers → SSO verified Anonymous Access and enable the switch SSO-Verified Anonymous Access in Kantega SSO Enterprisefor the Identity provider.

    image-20240214-145820.png

    Enable Force login in Kantega SSO Enterprise – SSO is applied to all URLs.

    image-20240214-145343.pngImage Removed
  3. Select Common → Force login. Enable the switch Require login to force anonymous users to login on public pages.

    force login.pngImage Added

  4. Configure Known domains in Kantega SSO Enterprise.
    You can trust the Identity Provider To make users not in known domains to stay anonymous, select the option “Trust identity provider to log in users only from the known domains, but fallback to SSO-Verified Anonymous Access for other users.

    image-20240214-145240.pngImage Removed

    See also how to make users not in known domains stay anonymous.

 

Skjermbilde 2024-09-03 kl. 12.48.28.pngImage Removed

Skjermbilde 2024-09-03 kl. 12.51.36.pngImage Removed

Skjermbilde 2024-09-04 kl. 10.08.42.pngImage Removed

Skjermbilde 2024-09-03 kl. 13.07.36.pngImage Removed

Skjermbilde 2024-09-03 kl. 13.06.40.pngImage Removed

Skjermbilde 2024-09-03 kl. 13.07.36.pngImage Removed

Configure SSO-verified Anonymous Access in Kantega SSO Enterprise

Select Identity Providers in the KSSO menu. The Identity Provider overview page is shown.

...

Choose the Identity provider you want to configure, then select SETTINGS → SSO-Verified Anonymous Access. Enable the switch SSO-verify anonymous access.

...

  1. known domains option 3.pngImage Added


Configuring related settings in Kantega SSO Enterprise

...

The Group Memberships settings allow configuring conditions for when the user is created. This can be configured fluently with SSO-verified 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.User login with IDP