Re: dovecot oauth

On 26/10/21 17:48, Aki Tuomi wrote: >> On 26/10/2021 16:04 la.jolie@paquerette wrote: >> >> >> Hello, >> >> I upgraded my servers from Debian Buster (v10) to Bullseye (v11). >> Before the upgrade, I had Roundcube / Dovecot working with LemonLdap >> (via OAuth). >> >> After the upgrade, i can't

Re: dovecot oauth

> On 26/10/2021 16:04 la.jolie@paquerette wrote: > > > Hello, > > I upgraded my servers from Debian Buster (v10) to Bullseye (v11). > Before the upgrade, I had Roundcube / Dovecot working with LemonLdap > (via OAuth). > > After the upgrade, i can't connect to Roundcube anymore. > > -

Re: dovecot oauth

On 6/07/20 15:23, la.jolie@paquerette wrote: > On 5/07/20 18:46, Aki Tuomi wrote: >>> On 05/07/2020 19:43 Aki Tuomi wrote: >>> >>> On 04/07/2020 21:12 la.jolie@paquerette wrote: Hello, I'm trying to configure roundcube / dovecot to work with keycloak. I

Re: dovecot oauth

On 5/07/20 18:46, Aki Tuomi wrote: >> On 05/07/2020 19:43 Aki Tuomi wrote: >> >> >>> On 04/07/2020 21:12 la.jolie@paquerette wrote: >>> >>> >>> Hello, >>> >>> I'm trying to configure roundcube / dovecot to work with keycloak. >>> I activated xoauth2 oauthbearer in dovecot. >>> But a problem

Re: dovecot oauth

> On 05/07/2020 19:43 Aki Tuomi wrote: > > > > On 04/07/2020 21:12 la.jolie@paquerette wrote: > > > > > > Hello, > > > > I'm trying to configure roundcube / dovecot to work with keycloak. > > I activated xoauth2 oauthbearer in dovecot. > > But a problem occurs when dovecot tries to

Re: dovecot oauth

> On 04/07/2020 21:12 la.jolie@paquerette wrote: > > > Hello, > > I'm trying to configure roundcube / dovecot to work with keycloak. > I activated xoauth2 oauthbearer in dovecot. > But a problem occurs when dovecot tries to contact the keycloak server > (logs are below). > > My problem

Re: Dovecot & OAuth

Op 10-12-2019 om 16:44 schreef mizuki: Thank you Stephan, I'm wondering if I can read the track of the status of bug reports? Could you please advice? No, this is for our own internal reference. Thanks. Mizuki On Sun, Dec 8, 2019 at 6:40 AM Stephan Bosch >

Re: Dovecot & OAuth

Thank you Stephan, I'm wondering if I can read the track of the status of bug reports? Could you please advice? Thanks. Mizuki On Sun, Dec 8, 2019 at 6:40 AM Stephan Bosch wrote: > > > On 06/12/2019 20:54, Aki Tuomi via dovecot wrote: > > Hi! > > > > It seems there is a bug in the oauth2

Re: Dovecot & OAuth

On 06/12/2019 20:54, Aki Tuomi via dovecot wrote: Hi! It seems there is a bug in the oauth2 driver, it loads the cert files wrong way. I'll make an internal bug report of this. Tracking as DOP-1590. Regards, Stephan. On 06/12/2019 16:42 mizuki wrote: Hi, For troubleshooting

Re: Dovecot & OAuth

Great, thank you so much Aki! Please let me know when the fix is available and I will help test in our environment. We'd really like to enable this feature. Thanks again. Mizuki On Fri, Dec 6, 2019 at 2:54 PM Aki Tuomi wrote: > Hi! > > It seems there is a bug in the oauth2 driver, it loads the

Re: Dovecot & OAuth

Hi! It seems there is a bug in the oauth2 driver, it loads the cert files wrong way. I'll make an internal bug report of this. Aki > On 06/12/2019 16:42 mizuki wrote: > > > Hi, > > For troubleshooting purposes, I change the read/write permissions on the > certs and confirmed 'dovecot' can

Re: Dovecot & OAuth

I changed some of the tls options following the document, now config is following: tokeninfo_url = https://keycloak.com/auth/realms/mail/protocol/openid-connect/token introspection_url =

Re: Dovecot & OAuth

Before declaring it not ready for prime time, did you try setting tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt In the oauth2 configuration file as documented in https://doc.dovecot.org/configuration_manual/authentication/oauth2 ? Aki > On 05/12/2019 21:58 mizuki via dovecot wrote: >