I have the latest hashicorp vault running as a container on my docker desktop on W11. Long paths are enabled in registry and local group policy.
When creating a secret with CLI
vault kv put user/Users/5fdb6bcc-d227-4dc1-9e91-34f9fd92e379/Adapters/E483E775-64E1-4031-9913-701D5B4B081E test=123
I get an error like
rename /vault/file/logical/e61672f5-1e46-6c88-4f98-e92d584be7f9/d1c32029-93ec-e8ff-8fc0-63cddf7df326/metadata/5kL6rnykfyz4Ai2oMHzTmzGIeZetbcY7QKolNOZ4Em9C0mHmyWxhucGtwBsdGT/8Gd16lZ6ILpzgLEc8HiJIRfIMD76Z6Fqk8oztL6FmDbgd1icchdWA4PrSeZ4ySMzQzvwJbd6PeIj6Vjp0A4cjRaTDa6PArzNvIFKotbnmGJnPjBF6dhkUA8Lr/p0DsUAMSYQJyfnFWNxQqNyHjCYG5SnIyVquew79TlpNCKD8WioCXsSftD0h2vxQv1hL/_8Gdj9kf8Pi43ug5YMKXcVTXWvFGNXPeOEBgSpiDcWo30z1bN19GfED7RX31Q3DzAGHXd1xkfc5XTiD3PUiiz1rvv9q28SCH8GcfVYG1qGwdatt3UI2lSytP77.tmp /vault/file/logical/e61672f5-1e46-6c88-4f98-e92d584be7f9/d1c32029-93ec-e8ff-8fc0-63cddf7df326/metadata/5kL6rnykfyz4Ai2oMHzTmzGIeZetbcY7QKolNOZ4Em9C0mHmyWxhucGtwBsdGT/8Gd16lZ6ILpzgLEc8HiJIRfIMD76Z6Fqk8oztL6FmDbgd1icchdWA4PrSeZ4ySMzQzvwJbd6PeIj6Vjp0A4cjRaTDa6PArzNvIFKotbnmGJnPjBF6dhkUA8Lr/p0DsUAMSYQJyfnFWNxQqNyHjCYG5SnIyVquew79TlpNCKD8WioCXsSftD0h2vxQv1hL/_8Gdj9kf8Pi43ug5YMKXcVTXWvFGNXPeOEBgSpiDcWo30z1bN19GfED7RX31Q3DzAGHXd1xkfc5XTiD3PUiiz1rvv9q28SCH8GcfVYG1qGwdatt3UI2lSytP77 Path not found
I can navigate close to the last directory in File Explorer, but last one causes a bluescreen.
I can navigate to the the last directory in command prompt
I can’t navigate to the directories below /vault/file/logical/ due to permission issues
Hashicorp Vault does not find the secret and throws errors. Same does not happen with secret paths with less subpaths.
I guess, it’s due to some path length issues in W11. It used to work on W10.
Any ideas?
Thanks,
Holger