-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Remove spaces in group names that come from Entra #681
Comments
I hope you're doing well! I wanted to follow up on this issue and kindly request an update on its progress. Is there any timeline or additional information you could share regarding its resolution? Thank you for your efforts and support! |
Hi, sorry for the late reply.
The problem I see with this is that it would map different Entra groups to the same group: The Entra groups "My Group Name" and "my-group-name" would both be mapped to the "my-group-name" system group. |
An option would be to add some crc-like suffix to groups that have been renamed, so that they're always different. Or given that there's no risk of duplication just add a suffix and consider that suffix as "protected" for the groups that are synchronized otherwise. |
Not a fan of defining an arbitrary suffix as "protected" when such restriction can't be enforced in M365. Feels like it's just a matter of time until someone then intentionally creates a group with that name. I don't see any disavantage to appending a crc-like suffix though. |
Is there an existing request for this feature?
Describe the feature
When using authd with Microsoft Entra ID, group names containing spaces are harder to work with in Linux terminals.
A good solution would be to automatically replace spaces (" ") with dashes ("-") in group names retrieved from Entra.
Also to provide backwards compatibility, configuration option could be added in authd.yaml to enable or disable this transformation (e.g., transform_group_names = true).
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
The text was updated successfully, but these errors were encountered: