Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Granting users product access based on domain after their access was removed

Nicholas Hagopian-Zirkel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 27, 2021

Summary

In order to limit the number of users on our license, I remove Jira Access for users who have been inactive for over 90 days. We also give users site access automatically if they have an "approved domain". Unfortunately, users whose Jira Software access I have removed due to inactivity do not regain access automatically when logging in despite having an approved domain. Instead they get this error: 

The page isn’t redirecting properly
An error occurred during a connection to tds-jira.atlassian.net.
This problem can sometimes be caused by disabling or refusing to accept cookies.

Is this error normal? I thought I tested this before and got different behavior. Specifically that those users regained site access without interference. 

Attempted solutions:

- Testing if the issue actually does have to do with disabled cookies. 

- Testing if it's related to the browser. (suggested in this thread

- Testing if it's related to adblock. (suggested in this thread)

All these solutions ignore that fact that the error only occurs with specific users who have had their Jira access revoked. 

 

Jira access is configured as follows:

Capture.PNGGroup access:

Capture1.PNG

 

User who has full access (the error does not occur for them):access.PNGUser who has been removed due to inactivity for 90 days (this error does occur for them):noaccess.PNG

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 5, 2021

Hi @Nicholas Hagopian-Zirkel  -- Welcome to the Atlassian Community!

You note that you tested this and it worked, and now it does not.  If you haven't changed any of the configuration settings since your testing, I recommend that you submit a ticket to support for this.  They will be able be able to see what you see when you grant them access to the instance.

As the site admin for a paid instance, you may submit that report here:

https://support.atlassian.com/contact/#/

Once you learn more and resolve this, please post back here so others can benefit from the information.  Thanks!

Best regards,

Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events