Closed msakrejda closed 7 years ago
So the issue is that we were not filtering XHRs properly in our auth middleware, and we would in some situations send a 301 to the client to hit our oauth endpoint directly--which obviously can't work. The fix is entirely on us and there is no issue in identity.
Thanks for the follow up 👍
We occasionally see this error when talking to
id.heroku.com
:(see https://github.com/heroku/herokudata/issues/368). I don't think it's an
identity
issue per say, but I figure it may be familiar. I think this happens during our oauth token refresh, but I'm not sure why or how. Have you seen this before? Do you know what we might be doing wrong?