[enhancement]: OAuth client authentication

[jip149]

Which feature or improvement would you like to request?

I'm trying to connect an oidc client using stalwart as oidc provider.

The client does not implement dynamic client registration, so I need to manually register an oauth client and get a client id and secret.

I tried adding an oauth client through the webui but I cannot get a secret for the oauth client. I also could not find a way to link an oauth client to an api key.

Is your feature request related to a problem?

I'm having a problem with...

Code of Conduct

• I agree to follow this project's Code of Conduct

[TheLonelinessOfHS]

Same question here!

[mdecimus]

I tried adding an oauth client through the webui but I cannot get a secret for the oauth client. I also could not find a way to link an oauth client to an api key.

You can create an API key that has permissions to register new OAuth Clients. But if you mean setting a client secret to authenticate users, this is not yet supported.

[TheLonelinessOfHS]

I tried adding an oauth client through the webui but I cannot get a secret for the oauth client. I also could not find a way to link an oauth client to an api key.

You can create an API key that has permissions to register new OAuth Clients. But if you mean setting a client secret to authenticate users, this is not yet supported.

Thanks. Could you please support full oidc clients that comes with app id and secret if possible? This is an important feature that I believe many others also desperately want. In this way, self hosters can have identity management & Auth systems that use stalwart as oidc provider, such that the users of many other APPs (e.g. Nextcloud) can share a same set of credentials with the mail server (stalwart).

[mdecimus]

Could you please support full oidc clients that comes with app id and secret if possible?

Sure, just renamed the issue.

[TheLonelinessOfHS]

Could you please support full oidc clients that comes with app id and secret if possible?

Sure, just renamed the issue.

Awesome! Thanks so much!

[jip149]

Not sure if these should be separate issues, but ideally for a perfect setup with stalwart-mail as oidc provider, it would be very useful to have:

• documentation of available scopes and fields
• groups and roles information
• custom fields for accounts, groups, roles

[TheLonelinessOfHS]

Not sure if these should be separate issues, but ideally for a perfect setup with stalwart-mail as oidc provider, it would be very useful to have:

• documentation of available scopes and fields
• groups and roles information
• custom fields for accounts, groups, roles

From my point of view, some of them are good. The others, like custom fields, should not be handled by stalwart which is a mail platform. Ideally, the user can use a dedicated identity provider like KeyCloak to handle this and use stalwart as a backend.