This is an issue in 23.9.X. We plan to have a fix in 23.10.X, or you can try using an older version (for example, 23.8.X).
The underlying problem is that the schedd currently assumes that if userA@xxxxxxx, userA@xxxxxxx, and UserA@xxxxxxxxxxx all submit jobs, those jobs should be run as OS account userA on the local system. Weâre starting to have the schedd distinguish between
these identities, so that a userA from a remote organization either cannot submit jobs or those jobs are run under a generic account.
An immediate fix for you is to issue a new IDToken with identity usera@xxxxxxx, following your example names. Or you could change the UID_DOMAIN parameter in the scheddâs configuration to hostname.fqdn.
- Jaime
|