View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005184||SOGo||Web Address Book||public||2020-10-15 11:48||2020-10-20 12:13|
|Platform||[Server] Linux||OS||RHEL/CentOS||OS Version||7|
|Summary||0005184: Maintain contact details of users in the global address book|
It should be possible to add or maintain user contact data from the authentication source.
MySQL is used as authentication source. The source contains only the data necessary for authentication (like username and password) and the parameter isAddressBook is enabled. The users are provided with the elementary data (username as display name and email address). Contact data of users in the global address book cannot be edited or supplemented. This "problem" will probably also occur with LDAP as authentication source. And no, it is not desired to maintain the contact data in the authentication source (the reason for this is for example the EU-GDPR).
Since contact data can be added and maintained in other address books, the necessary data structure already exists and it might only be necessary to allow editing in the global address book and to overlay/enrich the data from the authentication source.
|Steps To Reproduce|
|Tags||No tags attached.|
You can copy an address card from the global address book to one of your own address books, and edit it there.
No Christian, maybe I didn't describe the feature request in enough detail. But I think you are forgetting the special features of the global address book here.
But let me give it a try. I am sure we agree that the following applies:
So we have to set the parameter isAddressBook=YES for our authentication source (is equal to user source).
If for reasons (e.g. EU-GDPR) only the mandatory data should be included in the authentication source, the result is a incomplete address book. Because it contains only username and e-mail address.
As a workaround, it would be possible (as you suggested?) to have an additional address book maintained by a user, who then shares this address book with all other users and also activates the option "Subscribe User". The latter only works for existing users and not for "Any authenticated User". This in turn means a lot of effort when setting up a new user. But okay, it would be one way.
But with this workaround, the incomplete global address book is still there and we deprive ourselves of such nice features like the already automatically shared global address book (on all channels like CardDAV, EAS, etc.).
So from our point of view it would be great if the data from the authentication source could be enriched directly in SOGo. Because the UI for this is available and great implemented. The authentication source can remain read-only as before, new data simply ends up in the corresponding SOGo table in SQL.