Nov Matake
Nov Matake
I couldn't reproduced the error in this sample app. https://github.com/nov/doorkeeper-openid_connect-sample Are you missing `app/models/oauth.rb` which defines `Oauth` constant?
Ah, because you have `oauth` gem, `OAuth` is already defined...
It seems because of Sorcery bug, which should be fixed in Sorcery v1. https://github.com/Sorcery/sorcery/issues/316 https://github.com/Sorcery/sorcery/issues/312#issuecomment-1130370988 Does doorkeeper-openid_connect need some changes?
can't you install `tzdata` via apt?
I have no plan.
Since I switched httpclient gem to faraday, I might do such thing in faraday middleware layer. Still just an idea though.
made the middleware https://github.com/nov/faraday-jwt
Can you try v2.2.0 of this gem with `faraday-jwt` gem? With this custom config, you can probably handle JWT response as JSON. ```ruby OpenIDConnect.http_config do |config| config.response :jwt end ```...
Underling OAuth2 gem supports MTLS client auth & MTLS access token. https://github.com/nov/rack-oauth2/blob/master/lib/rack/oauth2/client.rb https://github.com/nov/rack-oauth2/blob/master/lib/rack/oauth2/access_token/mtls.rb You can simply use them, or following the underling gem structure, you can define MTLS access token...
could you try this? https://github.com/nov/openid_connect/pull/76