You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the issue #243 in the gin-swagger repo, and swaggo/swag#871:
Is your feature request related to a problem? Please describe.
OAuth2 clients that only support Authorization Code Flow with PKCE do not work with the current feature set of echo-swagger.
Describe the solution
Add Proof Key for Code Exchange support. There is a flag for it in Swagger UI 3.24.0+. The flag in Swagger UI is usePkceWithAuthorizationCodeGrant.
In the corresponding Pull Request I added an additional attribute to the OAuthConfig struct called "UsePkce" which configures the boolean parameter for "usePkceWithAuthorizationCodeGrant" in the "initOAuth" part of the index template.
With this small change, the auth flow works as expected.
The text was updated successfully, but these errors were encountered:
Similar to the issue #243 in the gin-swagger repo, and swaggo/swag#871:
Is your feature request related to a problem? Please describe.
OAuth2 clients that only support Authorization Code Flow with PKCE do not work with the current feature set of echo-swagger.
Describe the solution
Add Proof Key for Code Exchange support. There is a flag for it in Swagger UI 3.24.0+. The flag in Swagger UI is usePkceWithAuthorizationCodeGrant.
In the corresponding Pull Request I added an additional attribute to the OAuthConfig struct called "UsePkce" which configures the boolean parameter for "usePkceWithAuthorizationCodeGrant" in the "initOAuth" part of the index template.
With this small change, the auth flow works as expected.
The text was updated successfully, but these errors were encountered: