Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Username & password still working after SAML/SSO integration

After configuring SAML for SSO,  and provisioning the app for users in Okta. Launching the APP from the Okta dashboard reflects an error and to try to login again. It allows me to use username/password. This is true in Chrome or Incognito Chrome.

How do I enforce SSO to be the ONLY method to authenticate?

1 answer

0 votes
Dave Meyer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 24, 2020

@Joy Knox if you've configured SSO, it should be strictly enforced on all your organization's managed accounts (users with email addresses on a domain you've claimed).

If you're seeing behavior where this is not the case, I would recommend contacting Atlassian support, as this is a security risk and not intended behavior.

We had users configured before SSO, it seems like the users created before SSO aren't working and only new users provisioned thru SSO are connecting via SSO. But what's frustrating is that both User/pass and SSO are working and not requiring SSO for all access.

I'll create a support request.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events