-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: integrate with fosite v0.40
(go-jose migration)
#2526
Conversation
If you are fine with those changes and once fosite's PR is merged, I can update this PR so that hydra can immediately integrate with latest |
Sorry, I always have to manually trigger the github actions CI pipeline to see if OIDC passes. |
v0.40.0
(go-jose migration)
v0.40.0
(go-jose migration)v0.40
(go-jose migration)
@aeneasr once all checks pass this PR can be merge. |
Thank you! I've merged the fosite PR and released it as v0.40.2 |
great! |
@@ -27,7 +27,7 @@ import ( | |||
"net/http/httptest" | |||
"testing" | |||
|
|||
jwtgo "github.com/dgrijalva/jwt-go" | |||
jwtgo "github.com/ory/fosite/token/jwt" | |||
"github.com/stretchr/testify/require" | |||
|
|||
"github.com/ory/fosite/token/jwt" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be nicer to have just single import here, "github.com/ory/fosite/token/jwt"
, no need for both "github.com/ory/fosite/token/jwt"
and jwtgo "github.com/ory/fosite/token/jwt"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, grouping of imports is now wrong.
Related issue
Proposed changes
This PR shows the required changes to integrate Hydra with Fosite's PR #593
Checklist
Further comments