Failed to execute 'text' on 'Response': body stream already read

[cclement-perrin-acoss]

Describe the bug When trying to log on Vault server with LDAP authent, I have got an error message: Failed to execute 'text' on 'Response': body stream already read.

The only option is "Logout". Iam not able to search any secret.

Expected behavior No error message

Browser (please complete the following information):

• OS: Win10
• Type Chrome
• Version: Version 98.0.4758.102

[ticktostick]

same problem here

chrome:100.0.4896.127 released:2.3 Vault 1.10.0

[mwxp06]

Same problem :( @mulbc Do you have any plan with this tool, os id dead now?

Thank you

[mulbc]

I haven't forgotten about this issue, but haven't had time to look closer at this. If you find the issue in the meantime, feel free to send in a PR. That will definitely fix the issue faster

[tamere-allo-peter]

Same problem here.

VaultPass 2.3, with Chrome 101.0.4951.64 (Build officiel) (64 bits) on System: Kernel: 5.4.0-110-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 wm: xfwm4 dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal

LDAP auth works fine from Vault's GUI or Vault's API. Vault installed from docker.io/hashicorp/vault

[mulbc]

I just extended the dev setup script to include LDAP. Unfortunately I am not able to reproduce all your problems. LDAP login "just works" for me

[mulbc]

I found a section in the code where we execute .text() twice on the same resource in case we have issues loading the secrets. Maybe you're hitting that, but that would mean your LDAP (or usermapping) isn't configured correctly. I'll package a new release real quick and ship it out in case that fixes that issue. If that is the case, you will need to fix your Vault LDAP config though.

[ticktostick]

The error has gone the problem is solved its working now

[mulbc]

Thanks for confirming! I'll close the issue then