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
Is your feature request related to a problem? Please describe.
I'm trying to integrate a declarative Swagger API with Zitadel. I've been using OAuth2AccessCode, but the redirect URI is set to /oauth2-redirect.html, while the documentation has users host the swagger docs at something like /swagger/*. Additionally, there does appear to be a way to set a default clientId.
I see you have been directing users to file an issue with the client repo instead (such as https://github.com/swaggo/echo-swagger). If this is still the case, feel free to close.
Is your feature request related to a problem? Please describe.
I'm trying to integrate a declarative Swagger API with Zitadel. I've been using OAuth2AccessCode, but the redirect URI is set to
/oauth2-redirect.html
, while the documentation has users host the swagger docs at something like/swagger/*
. Additionally, there does appear to be a way to set a defaultclientId
.Describe the solution you'd like
clientId
usePkceWithAuthorizationCodeGrant
(https://swagger.io/docs/open-source-tools/swagger-ui/usage/oauth2/)oauth2RedirectUrl
(https://swagger.io/docs/open-source-tools/swagger-ui/usage/configuration/)Is there something I'm missing in order to configure it properly?
The text was updated successfully, but these errors were encountered: