Skip to content
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

Provision aliases based on an LDAP attribute #5173

Closed
ChristophWurst opened this issue Jun 14, 2021 · 1 comment · Fixed by #5198
Closed

Provision aliases based on an LDAP attribute #5173

ChristophWurst opened this issue Jun 14, 2021 · 1 comment · Fixed by #5198

Comments

@ChristophWurst
Copy link
Member

Feature Request

Allows admins to optionally configure aliases for provisioned accounts. Since LDAP is already a popular choice for a user back-end of Nextcloud, we can build this feature around LDAP. The admins will have to enter the attribute name and we use \OCP\LDAP\ILDAPProvider::getUserAttribute to fetch the alias email address.

If LDAP isn't available (\OCP\LDAP\ILDAPProviderFactory::isAvailable) then we should hide this setting from the admin.

The attribute could be multivalued if more than one alias is set. We have to check if/how \OCP\LDAP\ILDAPProvider::getUserAttribute supports this because it currently always returns a string. Taking a quick look at the implementation tells me only the first result will be returned if the value is an array. This means we might have to change the server API to allow multiple values, e.g. in a getUserAttributes or getUserMultiAttribute

Summary

Provision aliases based on LDAP attributes.

@kesselb
Copy link
Contributor

kesselb commented Jun 16, 2021

PR for server to read multi-value attributes: nextcloud/server#27515

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants