You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the containerfile we have installed google-authenticator in the container. After having the container deployed to the physical server, the google authenticator PAM module can not open/write the .google-authenticator file. The file rights and owner seem to be correct.
Dec 15 13:13:30 ses2-hypervisor-test login(pam_google_auth)[2060]: Failed to create tempfile "/var/home/admin/.google_authenticator~ovZ6Nd": Permission denied
Dec 15 13:13:30 ses2-hypervisor-test login(pam_google_auth)[2060]: Failed to update secret file "/var/home/admin/.google_authenticator": Permission denied
35963568 4 -rw-------. 1 admin admin 181 Dec 15 09:08 .google_authenticator
As root or admin I can open and edit .google-authenticator
For the moment SELINUX has been disabled. In readonly mode everything works as expected.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
From the containerfile we have installed google-authenticator in the container. After having the container deployed to the physical server, the google authenticator PAM module can not open/write the .google-authenticator file. The file rights and owner seem to be correct.
As root or admin I can open and edit .google-authenticator
For the moment SELINUX has been disabled. In readonly mode everything works as expected.
Has anyone seen this?
Beta Was this translation helpful? Give feedback.
All reactions