Relationship Graph

View IssueDependency GraphShow Summary
Relationship Graph
related to related to child of child of duplicate of duplicate of

View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001810SOGoBackend Mailpublic2012-05-21 11:022017-01-19 09:50
Reporterokroeger Assigned To 
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status newResolutionopen 
Summary0001810: Authentication via IMAP
Description

This feature request is basically a +1 for the one voiced at:
https://inverse.ca/sogo/lists/arc/users/2011-12/msg00304.html

At our institution we have a very complicated authentication architecture; to put a long story short, we can neither use LDAP or CAS to authenticate users. Presently, we use OpenXChange, which allows to auth against our IMAP server. A similar functionality in Sogo would allow us to migrate.

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
related to 0002634 new Support for separate/multiple AUTH and USER Db's, like dovecot 
has duplicate 0002225 resolvedludovic IMAP-based authentication 

Activities

ludovic

ludovic

2012-05-22 15:53

administrator   ~0003936

If we support authentication over IMAP, we couldn't show the user's full name (since we wouldn't have a way to get it) nor email addresses other than the system one (uid@SOGoMailDomain).
okroeger

okroeger

2012-05-23 11:10

reporter   ~0003966

Sorry, I should have been clearer. We can provide names, e-mail-addresses, and other user data via an SQL database or LDAP, but we cannot use either for authentication. Put simply, we'd just need password checking to be done via IMAP. Apparently, this also is also true for the three users who discussed this feature request on the mailing list.
tanstaafl

tanstaafl

2014-03-06 12:50

reporter   ~0006651

I created a new feature request yesterday before finding this one, that would cover this use case and then some...

"Support for separate/multiple AUTH and USER Db's, like dovecot"

http://www.sogo.nu/bugs/view.php?id=2634
ivit

ivit

2014-03-10 11:20

reporter   ~0006676

Maybe hybrid solution with SQL user datasource and type = imap, could address problem of unknown user's details (e.g. full name).

Basically, we could have one (table or view) which keeps only user info (same as sql user source), and we could have IMAP server info which can be used for authentication.

IMAP server should be configurable per user and per user source. IMAPHostFieldName user source (or user info) could be used to authenticate.
aceton1k

aceton1k

2016-08-31 09:10

reporter   ~0010627

+1 for this feature, makes perfect sense.
FoZo

FoZo

2017-01-19 09:50

reporter   ~0011230

Any update here?

Issue History

Date Modified Username Field Change
2012-05-21 11:02 okroeger New Issue
2012-05-22 15:53 ludovic Note Added: 0003936
2012-05-23 11:10 okroeger Note Added: 0003966
2014-03-06 12:50 tanstaafl Note Added: 0006651
2014-03-07 13:47 Christian Mack Relationship added related to 0002634
2014-03-09 21:06 ludovic Relationship added has duplicate 0002225
2014-03-10 11:20 ivit Note Added: 0006676
2016-08-31 09:10 aceton1k Note Added: 0010627
2017-01-19 09:50 FoZo Note Added: 0011230