Safe to change authentication policies of a user?

Kapil Joshi November 12, 2024

Hey folks,

I have two authentication policies in Atlassian guard. Is it okay if I change a policy for a particular user? Will it break anything? 

I expect it will only change user's login experience. Is there anything I should be aware of?

Thank you.

EDIT: Expecting answers from someone who has done this. Not an AI generated answer. My two policies are working just fine. Just want to know what could be the consequences of switching between the two, if any.

2 answers

1 accepted

1 vote
Answer accepted
Hector Menchaca
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 13, 2024

Hello @Kapil Joshi ,

Thanks for contacting Atlassian Community!

It depends - like for example if you change the user from the SSO policy to a Non-SSO policy then the user will not be asked to login with SAML SSO so in this case it affects and change the login process for the user and viceversa.

I think everything depends of the settings you have on your Authentication Policy and if you move the user to a policy that doesn't have these settings then it's gonna affect either the login or password requirement, etc...

Best regards,

Thanks!

Hector M

Kapil Joshi November 13, 2024

Thank you, Hector!

0 votes
iub fun November 12, 2024

Hello

Changing authentication policies for a user can be safe if done carefully, but it requires consideration of the potential impact on security and user access. It's important to ensure that new policies, such as password complexity or multi-factor authentication (MFA), are clearly communicated to the user to avoid disruptions. Additionally, always test changes in a controlled environment before implementing them on live systems to minimize risks and ensure a smooth transition without compromising security.

 

 

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events