We are unable to scale out phpmyadmin for multi instance session

Describe the bug

We are using phpmyadmin for wordpress. So when we are trying to save session in remote persistent storage then we get this error (ss attached below).
In session.save_path attribute in the php.ini file when i am putting '/home/site/php/tmp" then it is throwing a white page error. I have attached a screenshot for the same.
This is happening because of user mismatch , i.e. the user of persistent remote stoarage folder is nobody while phpmyadminserver runs as nginx or root user.
When we use local storage to store sessions then this issue is not coming, but by doing that we are unable to scale up our Wordpress website.

So, is there a way to avoid this user id mismatch? I mean is there some code in the folder which checks for user id mismatch so that we can go past that?

Or could you please suggest any other solution?

To Reproduce

Try saving phpmyadmin session in multi instance remote storage.

Expected behavior

phpmyadmin should not throw white page error

Screenshots

Server configuration

• Operating system:
• Web server:
• Database version:
• PHP version: 8.2.9
• phpMyAdmin version: 5.2.1

Client configuration

• Browser: Same problem with all the browser even after clearing cookies
• Operating system: Linux

Additional context

Add any other context about the bug here.

Start with the session.save_path setting in php.ini and reproduce the white-page error using remote persistent storage for a multi-instance deployment. Check the reported PHP 8.2.9 and phpMyAdmin 5.2.1 configuration, including the storage and process users. Done means sessions work with remote storage without the white-page error.