Vault: Bug Vault UI - can't choose sign in method from Safari

[gabyfulchic]

Describe the bug
The bug is a 400 bad request when reaching "method" on the vault sign-in page.
But only when using Safari.

To Reproduce
Steps to reproduce the behavior:

1. Go to vault url
2. Go to sign in "methods"
3. And see in the console the "400 bad request"

Expected behavior
Normally you can choose to sign in by token, ldap, github etc ...

Environment:

• Vault Server Version (retrieve with vault status): 1.1.3
• Vault CLI Version (retrieve with vault version): 1.1.3
• Server Operating System/Architecture: Debian 9

Can you reproduce it yourself ? ;)

Warmly,
FULCHIC gaby.

[noelledaley]

Hey there! Thanks for filing this issue. Could you share a screenshot or additional steps to reproduce? Which auth method are you selecting from the dropdown? Let me know and we can dig more into it. Thanks!

[gabyfulchic]

Hello @noelledaley,

Yeah sure, that's it :

You're welcome!
And thanks for responding that fast !

[noelledaley]

Hi @gabyfulchic, thanks for the screenshot! What version of safari are you using? I still haven't been able to reproduce this unfortunately. :/

[gabyfulchic]

Hey @noelledaley,

I’m using safari 13.0.1
(14608.2.11.1.11)

Can i give you More informations or is it ok now ?😁

Best Regards,

[noelledaley]

Hi @gabyfulchic, thanks for the information. We still haven't been able to reproduce this, which is strange. Could disabling your browser extensions or opening the page in a private window? Thanks!

[gabyfulchic]

We've tried without extensions and in a private window, it's the same thing. A strange shape is appearing and safari went in not responding and we have to force quit it !
As you can see on the .gif above. 😁

[noelledaley]

A-ha! I think we found the culprit. Sounds like this is an issue with Safari on Mojave. We had the same problem in Terraform Cloud. Thanks for bringing this to our attention -- I'm working on a fix! 🔧

[gabyfulchic]

Thank you for your time @noelledaley and good luck !

[noelledaley]

Thanks @gabyfulchic! This is fixed and will be included in our 1.3.1 release. :)