It's always nice when Murphy strikes. Today a new piece of software (beta) was to be presented to a customer. The creator of the software is on vacation and you can guess three times what happened. The software was tested again internally and it turned out that the login did not work.
As I am responsible for hosting and publishing, I was of course the first to be confronted with the problem. So let's take stock first:
- the application throws a 401 when logging in (kong throws 401 the app says auth ok)
- the error does not occur for everyone
- the login data does not play a role either (the same login data works for client a but not for client b)
- the publication (nginx) is correct as the error also occurs via internal URLs (no incorrect http headers)
After some trial and error I noticed an en in the actual login url. and YES it depends on the language setting of the selected browser. My Linux speaks English to me and that's why I got the error. After I changed my browser to German I was able to log in. Small error huge effect!
