# Percona MongoDB with vault **URL:** \ **Category:** Percona Server for MongoDB\ **Created:** [March 3, 2021, 9:50am UTC](https://forums.percona.com/t/percona-mongodb-with-vault/9520 "2021-03-03T09:50:23Z")\ **Posts on this page:** 1\ **Showing post:** 25
**Author:** ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)\ **Post date:** [September 10, 2025, 6:58pm UTC](https://forums.percona.com/t/percona-mongodb-with-vault/9520/25 "2025-09-10T18:58:16Z")
Isn’t it the same problem as you posted here? > [@Docker Setup with Vault Encryption key, "token are too open"](https://forums.percona.com/t/docker-setup-with-vault-encryption-key-token-are-too-open/39199/2): > > Hi @MohamedAziz Thanks for the question and congrats on your first post - welcome to the Percona Community! You’re fighting against the designed behavior of Docker Secrets. Docker mounts secrets as read-only files with 0444 (-r--r--r--) permissions owned by root. You cannot change this directly. The MongoDB process, for security reasons, refuses to use a token file that is world-readable. The solution is to create an entrypoint script that copies the secret to a new location, sets the correct… --- _[View the full topic](https://forums.percona.com/t/percona-mongodb-with-vault/9520)._