Dear all, We have found the cause of and fixed this issue, so it should now be resolved for all affected users. The problem was an obscure bug affecting up to 2.5% of active users by preventing proper login session persistence. It was caused by a security enhancement present in a web framework upgrade carried out earlier this year interacting with the RIPE Access single sign-on service. Apologies to all affected users. If you believe that you are still experiencing this (or any other) issue, please do not hesitate to let me know. Kind regards, Chris Amin and the RIPE Atlas team On 2015-07-20 15:39, Robert Kisteleki wrote:
On 2015-07-16 1:23, Yang Yu wrote:
I have been having this issue with every feature that requires logging in on https://atlas.ripe.net.
For instance, when I try to create an API key, HTTP POST to /keys/create/ gets a 302 to https://atlas.ripe.net/login?next=/keys/create/, then the new GET results in another 302 to https://atlas.ripe.net/keys/create/ and back to https://atlas.ripe.net/login?next=/keys/create/ until the browser gives up on redirecting and throws an error.
Tested on Chrome/Firefox with Ubuntu trusty and Windows 7. Tried on a different computer from a different continent, still the same issue.
Dear All,
We've heard others reporting this issue as well. We have been, and still are looking into it. We can confirm that the issue is real, but it proves difficult to track down the root cause.
We'll report back with our findings, and hopefully a solution too, shortly.
Regards, Robert Kisteleki, for the RIPE Atlas team