I worked around this bug, having to append the url

otocol/openid-connect/token/?token=eyJhbGciOiJSUzI1NiIsInR5c

But having this
Got 405 response for request [Req1: GET https:/
Method Not Allowed (took 16 ms + 41 ms in queue)

Change to POST? 

> I am getting first
> 
> Using 1 idle connections to handle 1 requests (1 total connections
> ready)
> Claimed request [Req2: GET https:
> No more requests to service for this peer (1 connections exist, 0
> pending)
> 
> and then the 404
> 
> Got 404 response for request [Req2: GET https:/
> 
> This should work with 2.3.16?
> 
> >
> > > Does anyone have a current config example using openid and with
> > > roundcube. I like to add this next to 'regular' logins'. I was able
> to
> > > login once but know I am getting these in the logs
> > >
> > > " No requests to service for this peer (1 connections exist, 0
> > pending)"
> > >
> > >
> > > I have added the 2 passdb with links to dovecot-
> oauth2.token.conf.ext
> > > from this manual[1], but it is not really clear if I need these and
> > can
> > > just add a config file with openid_configuration_url
> >
> > And after keycloak login, I am having these and do not get the
> > redirection to the login.
> >
> > oauth2 failed: Token validation failed: Invalid token
> > _______________________________________________
> > dovecot mailing list -- dovecot@dovecot.org
> > To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Reply via email to