Update OIDC DevUI to accept hybrid application types #28408
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor update to
provider.html
to treathybrid
application types the same way asservice
types - sincehybrid
types will either do the bearer token verification (with Dev UI sending them) or will start a code flow if the token is not available.The main reason, apart from supporting the
hybrid
applications directly, is to help testingweb-app
applications - the docs recommend to switch such applications toservice
in devmode for DevUI be more useful - buthybrid
is a better option in such cases, as a direct browser to Quarkus calls will be still handled in theweb-app
mode, whilehybrid
will also let OIDC Dev UI treat it the same way it doesservice
(with Swagger UI support, etc)