robotsnoindex
robotsnoindex


Available authentication policy settings for your organizations

With authentication policies, you configure settings for different sets of users. These sets of users come from your managed accounts. When you test settings on a small set of users, you reduce the risk of rolling out an error to your entire organization.

You need a subscription with Atlassian Access to create more than one authentication policy and apply single sign-on (SSO) and two-step verification to an authentication policy. The settings you can configure through authentication policies are:

Setting

Description

Requires Access

Single sign-on through SAML or G Suite

Enforce members to log in to Atlassian products with your identity provider.

Two-step verification

Require members to set up and use a second step when logging in.


Make it optional to set up and use a second step when logging in.


Password requirements

Choose minimum strength for user passwords.


Choose when a password expires.


Idle session duration

Choose how long members can be idle before we log them out.


Add settings to your authentication policies

Single sign-on (SSO)

SSO allows your users to log in using your organization's identity provider to access all your Atlassian cloud products. Create one authentication policy to test an SSO configuration on a few accounts before turning it on for your whole organization.

Set up SSO for SAML or G Suite

When you select SAML SSO, you’re redirected from the authentication policy to the SAML SSO configuration page. Learn how to configure SAML SSO.

When you select G Suite, you’re redirected from the authentication policy to the G Suite setup page. Learn how to set up G Suite SSO.

Once you’re done configuring SAML SSO or G Suite SSO, you need to enforce SSO in the policy.

To enforce SSO:

  1. Navigate to Authentication Policies at admin.atlassian.com.

  2. Select Edit for the policy you want to enforce.

  3. Select Enforce single sign-on.


Why are non-G Suite members unable to log in?

If you use a non-G Suite domain, members from that domain can’t log in.

Here's why this can happen.
When you enforce G Suite single sign-on for a default policy, non-G Suite members can’t log in.

This is how you can help these members to log in.
Create another policy for non-G Suite members so they can log in.

Enforce two-step verification

Two-step verification adds a second login step. The second step keeps the user accounts secure even if the password is compromised. When account logins are secure, your organization's products and resources are safer.

You can require members to set up and use a second step when logging in or make it optional.

If you enforce SSO, you can only set up two-step verification in your identity provider and not your authentication policy. Learn more.

Password requirements

You can choose the minimum strength that all passwords must comply with. By default, passwords do not expire. However, you can set an expiration period by defining the number of days for password expiration. 

If you enforce SSO, you can only set up password requirements in your identity provider and not your authentication policy. Learn more.

Idle session duration

Idle session duration is the amount of time a member stays logged in before we log them out, and they have to log back in. Learn more.

Add members to your authentication policies

Members come from your managed accounts, and you add them to different policies. Enter members individually or in bulk to your authentication policy.

To enter members individually:

  1. Navigate to Security > Authentication Policies at admin.atlassian.com.

  2. Select Edit.

  3. Select Members tab > Add members.

  4. Enter a user name or email address (only up to 20 users).

  5. Select Add.

To enter members in bulk:

  1. Navigate to Security > Authentication Policies at admin.atlassian.com.

  2. Select Edit.

  3. Select Members tab > Add members.

  4. Select Bulk entry > Select Upload to add CSV file (only up to 1000 emails from your managed accounts are allowed).

  5. Select Add.

We’ll notify you with an email when your bulk member update is complete. You can view your audit logs to check which members were added or could not be added. Learn more about audit logs.

Move members between your policies

You may need to move members from one policy to another policy. You can move individual members by using Change member’s policy or Add members. You can only move members in bulk by using Add members.

To change the policy for individual members:

  1. Navigate to Security > Authentication Policies at admin.atlassian.com.

  2. Select Edit for the policy the member belongs to.

  3. Select Members tab > Change member’s policy.

  4. Choose a different policy for this member.

To change the policy for members in bulk:

  1. Navigate to Security > Authentication Policies at admin.atlassian.com.

  2. Select Edit for the policy to move members to.

  3. Select Members tab > Add members.

  4. Select Bulk entry > Select Upload to add CSV file (only up to 1000 emails from your managed accounts are allowed).

  5. Select Add.

We'll add members to the new policy and apply the change next time the member logs in.

A member can only be in one policy at a time.