Implement configurable auth providers

Assigned to
9 months ago
8 months ago
No labels applied.

~bitfehler 9 months ago

Just for clarification: the ticket title says plural "providers", currently there is one. Is the goal to make that one configurable, to add others, or to make the configuration part of the generic interface?

~sircmpwn 9 months ago

Should have been more specific. The idea behind this ticket is to address this TODO:


By accepting a flag (-auth perhaps) which includes a connection string for the auth provider, e.g. imap://... or postgres://.... Then the scope of this ticket is parsing that URL, selecting IMAP from the list if imap:// or imaps:// is used, then rigging up the appropriate middleware.

~bitfehler 9 months ago

I pushed this to master, but it doesn't seem to pick up the "Implements:"? I figured this is mostly uncontroversial, but feel free to suggest style fixes or any specifics you had in mind, so I can get a better sense for your expectations/approaches/style/etc.:


~sircmpwn REPORTED IMPLEMENTED 9 months ago

LGTM. I would solve that TODO sooner rather than later, though.

~bitfehler 9 months ago

Conrad Hoffmann referenced this ticket in commit 071ee7c.

~migadu 8 months ago*

Just a bit of info on our preferred auth - we would like to use local CDB (constant db) lookups instead of sql or imap (as per my mail ~sircmpwn) For example using:


This is our preferred way for auth lookups at migadu and here it is preferred as it allows separation of DAV accounts from imap. We can expand on that later.

Register here or Log in to comment, or comment via email.