Feature: Modified usernames

[bill-taut]

Is there an existing request for this feature?

• I have searched the existing issues and found none that matched mine

Describe the feature

When logging in using an Entra email ID (e.g., [email protected]), the username and home directory on the VM are the full email address (e.g., /home/[email protected]).

For orgs with only one login domain, it would be great to have the username not include the @foo.com portion. So the username in this case would be bill and the home directory would be /home/bill.

Describe the ideal solution

No response

Alternatives and current workarounds

No response

System information and logs

No response

Relevant information

No response

Double check your logs

• I have redacted any sensitive information from the logs

[didrocks]

As a note: if we are going to support such feature:

• we need to take into account as the user name is used also for local group membership
• consequently, the user name should not conflict with any other local users on the machine and some checks should be done with some integration to ensure that you can’t add a local user afterwards either if the tools don’t do a nss request first

[shiv-tyagi]

Looks like a duplicate of #508

[bill-taut]

@didrocks We are using a network-mounted shared home directory. Given the lack of uniqueness and consistency guarantees with the current authd UID implementation, I actually want to add a local user with a known UID to every machine but without the ability to login using that local user. Logins would then be mediated by authd, but when they get in, the UID would be set according to the entry in /etc/passwd.

[adombeck]

consequently, the user name should not conflict with any other local users on the machine and some checks should be done with some integration to ensure that you can’t add a local user afterwards either if the tools don’t do a nss request first

At least useradd and adduser seem to check if the user already exists in NSS:

$ sudo adduser --allow-bad-names [email protected]
info: Allowing use of questionable username.
fatal: The user `[email protected]' already exists.
$ sudo useradd --badname [email protected]
useradd: user '[email protected]' already exists

[boonedoggle]

I also support adding this feature.