New Relic Login Flow Makes Me Angry
I have used New Relic recently because I wanted to explore and learn the platform. But logging in with password is a bit painful.
New Relic has this feature built in that you can have max 3 sessions open at a time. If you try to log in then, you will get to this page:
Hm, fine, I have to end at least one of these to be able to finish logging in. Ok, I end one of these, and New Relic will allow me to continue:
So far so good.
The trouble is that if I go through this flow, New Relic FE app then does not send the following request on inactivity:
https://login.newrelic.com/idle_timeoutThis request refreshes a token, so I can continue using New Relic after I go back after inactivity. No token, no resources, so I just get 401 and it redirects me back to the login page:
I always end up in this situation where I log in, end one session, then work in New Relic for a bit, then leave the tab open and go somewhere else, then go back, it gives me 401 and redirects me to the login page where I have to log in for the second time!
When I don’t have 3 sessions active at login, the /idle_timeout request is sent with no trouble, and I can continue using New Relic with no need to reauthenticate.
I don’t know if there is some deep reason behind this, but it feels like a buggy behaviour. Since I end one session at the beginning, it should allow me to stay logged in with 3 sessions. So the token should probably get refreshed. But that’s not what going on right now.
