Dependency Graph

Dependency Graph
related to related to child of child of duplicate of duplicate of

View Issue Details

IDProjectCategoryView StatusLast Update
0002634SOGoBackend Generalpublic2016-08-11 15:09
Reportertanstaafl Assigned To 
PriorityhighSeverityfeatureReproducibilityalways
Status newResolutionopen 
Platform[Server] LinuxOSDebianOS Version7 (Wheezy)
Product Version2.1.1b 
Summary0002634: Support for separate/multiple AUTH and USER Db's, like dovecot
Description

This would be extremely useful for any organization that may use a different system to manage email users than they use for Active Directory users.

Since SOGo only supports the use of Groups through LDAP/AD when assigning ACLs, we are unable to assign these via Grouyps. This means that I must add each and every user to the Company/Shared Calendars and Address Books, and I must update these each and every time I add or remove an employee.

This will be a major pain for me, and we aren't that big.

This problem would be completely alleviated if support for separate and multiple AUTH and USER DB backends was added.

TagsNo tags attached.

Relationships

has duplicate 0002632 closed SOGo Integrator Ability to use separate/multiple AUTH and USER Db's, like dovecot does now 
related to 0001810 new SOGo Authentication via IMAP 

Activities

Ivan Zakharyaschev

Ivan Zakharyaschev

2016-08-11 15:09

reporter   ~0010598

BTW, I'd like to note that several user dbs are already possible, with e.g.:

SOGoUserSources = (
{
type = ldap;
....
canAuthenticate = YES;
displayName = "GAL";
....
id = directory;
isAddressBook = YES;
},
{
type = ldap;
....
canAuthenticate = YES;
displayName = "GAL";
....
id = additional;
isAddressBook = YES;
}
);

Probably, only different ids are needed for this to work.

First, when reading this bug report, I thought having multiple user dbs would impossible currently, and this feature would need to be implemented.

But, actually, it turns out that only the part about separating the db into the password and user parts was an unimplemented requested feature.

(dovecot's configuration in this respect seems to be more flexible, of course, and perhaps, clear, because it allows different explicit kinds of merging several user dbs with the "skip", "result_success", "result_failure" parameters. I thought about suggesting defining several SOGoUserSources in your case, so that their results are merged, but then thought that it's not clear how the merging would happen, and it's not clear how to merge exactly the way you need.)

Issue History

Date Modified Username Field Change
2014-03-04 16:14 tanstaafl New Issue
2014-03-05 10:33 Christian Mack Relationship added has duplicate 0002632
2014-03-07 13:47 Christian Mack Relationship added related to 0001810
2016-08-11 15:09 Ivan Zakharyaschev Note Added: 0010598