Repository navigation
Conversation
…rootless Docker. The Docker section of the SSO guide set the keytab's owner and mode with sudo chown 33 on the host. With a rootless Docker daemon, user ID 33 inside the container maps to a different user ID on the host, so the container could not read the keytab and never became healthy. The guide now sets owner and mode from a throwaway container, which works with rootful and rootless daemons alike, warns against making the keytab world-readable, and adds a troubleshooting entry for an unhealthy SSO container.
ralf401
left a comment
There was a problem hiding this comment.
Thanks! Just a few thoughts at your discretion.
-
"Don't make the keytab readable for everyone (mode
0644) instead:" — theinsteadsits right in front of the colon, so it reads as if the clause after it were the alternative ("instead, anyone who can read it can act as…"), which is not what you mean. Moving it forward fixes the parse, for example: "Instead, don't make the keytab readable for everyone (mode0644): anyone who can read it can act as the Zammad service towards Active Directory." Even clearer is naming the temptation, since the paragraph otherwise warns against a workaround the reader was never offered: "Don't solve the permission problem by making the keytab readable for everyone (mode0644): anyone who can read it can act as the Zammad service towards Active Directory." -
Troubleshooting entry: "the keytab's owner or mode was set on the host" reads wider than the cause. The mode is harmless from the host, since chmod is not uid-mapped. A keytab with a host-side
chmod 0644is still readable as uid 33. Only the owner breaks, so dropping "or mode" would match the failure. -
The note covers three separate things: the rootless uid mapping, the warning against
0644, and how to replace the keytab later. The0644part is a security caveat and could stand as a.. warning::of its own, and the replacement line reads well as prose right after the command. -
$PWDassumes the reader is in the stack directory. The file list only says the files sit next todocker-compose.yml, so one clause ("from the stack's directory") would prevent a confused copy and paste.
|
Thanks for your feedback. Adjusted. |
The Docker section of the SSO guide set the keytab's owner and mode with sudo chown 33 on the host. With a rootless Docker daemon, user ID 33 inside the container maps to a different user ID on the host, so the container could not read the keytab and never became healthy. The guide now sets owner and mode from a throwaway container, which works with rootful and rootless daemons alike, warns against making the keytab world-readable, and adds a troubleshooting entry for an unhealthy SSO container.