cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Kieselhorst (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7137) Allow OAuth2 customization via Swagger2Feature
Date Sun, 19 Feb 2017 17:37:44 GMT

    [ https://issues.apache.org/jira/browse/CXF-7137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873764#comment-15873764
] 

Dennis Kieselhorst commented on CXF-7137:
-----------------------------------------

Well as you can see in the testcase the registration doesn't work, so in my view the added
code should be removed from CXF until Swagger allows proper configuration from outside. I'll
take a look at the Swagger code and maybe file an issue there.

> Allow OAuth2 customization via Swagger2Feature
> ----------------------------------------------
>
>                 Key: CXF-7137
>                 URL: https://issues.apache.org/jira/browse/CXF-7137
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS
>    Affects Versions: 3.1.8
>            Reporter: Alexander K.
>            Assignee: Sergey Beryozkin
>             Fix For: 3.2.0, 3.1.9
>
>
> It seems that there is no way to customize initOAuth() details like clientId, clientSecret,
realm, appName, etc. for SwaggerUI-OAuth integration. This will allow Swagger-UI authorization
for protected CXF REST services by an authorization server such as Keycloak.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message