Richer API Token settings and SAML Login Hint

Kantega SSO Enterprise v. 4.3.0 is finally out. We have now added more API Tokens configuration options, and usernames are forwarded to the IdP as login hints for a better 2-step login experience.
08/09/2020 - API tokens, SAML Login Hint

More control of API tokens

API tokens enable better authentication and integration of services with your Atlassian products. This release has added new features that give you greater control over who can create these tokens and where they can be used. IP restrictions lets you limit the network access, and User Permission gives you control over who can create tokens.

IP Address Restriction

Limit what IP ranges that are allowed to send API requests to your Atlassian environment. With the Deny and Allow mode, you have a wide range of possibilities for restricting IP addresses. Read more about IP restrictions.

Ip address restriction example

User Permissions

With the new user permissions settings, you get even more control over which users can create API tokens. Now, when you allow user-created tokens, you can restrict this ability to certain user groups. You can also limit the maximum duration of user-created tokens.

User permissions settings

You can read more about API tokens and how you can use them to set up integrations to Atlassian APIs in our documentation.

SAML Login Hint

Kantega SSO allows you to employ a 2-step login and automatically redirect a subset of users to a particular identity provider for SSO authentication. In release 4.3.0, we include a login hint when redirecting to identity providers, making this mode even better.

Login hint flow

For all identity providers supporting login hint, users will now only need to type their username once. The IdP will automatically pick up this value and prefill the username field for you.

You might also like

API Tokens

We are proud to release Kantega SSO Enterprise v. 4.1.0 with support for API Tokens. API tokens allow remote agents to establish personalized integrations with Atlassian APIs without compromizing user credentials
11/05/2020 - API tokens

Multi-factor authentication

Multi-Factor Authentication (MFA) verifies a user’s identity by requiring multiple credentials. In addition to username and password, MFA requires additional credentials, such as a code from the user’s smartphone, or a fingerprint.
23/10/2019 - sso, saml, mfa

Fast User Switch and SSO

This article shows how Kantega SSO Enterprise (K-SSO) can be used in combination with the Fast User Switcher (FUS) app from Actonic. Together these two apps gives system admins super powers. With K-SSO, users can sign in to Jira using the same identity as they use elsewhere in their work day. System admins can also configure and align multiple login mechanisms to balance security and usability. With FUS, system admins can also trouble shoot and configure Atlassian systems on behalf of users.
10/05/2020 - FUS, Actonic