I just finished a migration in the last week for a school based in Minnesota. We have switch active directories from internal directory to the state wide one. Users were prompted to login with your state email instead of their school one. Some of the users still tried logging in using their school email address which logged them into the customer portal. Could someone explain to me how they were able to still log in using an email that is not associated to a user in Atlassian Access but has definitely created tickets before. If someone needs more information to help me solve this issue please comment back and I can give any additional details. Ill post an example below.
Server address was Jones@MNCC.edu
changed active directory in cloud to state emails and user emails in server to match state emails.
Migrated to cloud
Logged in using old account email Jones@mncc.edu and can access the customer portal but not internal.
Using the state email it is business as usual for these users.
The User will be able to login to the Customer Portal if the below setting is applied :
If you have allowed "MNCC.edu" domains to login or create their own domains.
If you want to control who gets access to the Customer Portal access would recommend using "Don't allow customers to create their own accounts" in the Portal Access setting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.