cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7137) Allow OAuth2 customization via Swagger2Feature
Date Mon, 13 Feb 2017 12:00:46 GMT

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

ASF GitHub Bot commented on CXF-7137:
-------------------------------------

GitHub user deki opened a pull request:

    https://github.com/apache/cxf/pull/236

    CXF-7137: extended unittest to show non working security definitions

    I've extended the unittest to show that the implementation from CXF-7137 isn't working
at the moment. While contact is part of the BeanConfig and correctly serialized, the SecurityDefinitions
are not shown in the swagger.json as Swagger's BaseApiListingResource handles only the attributes
from BeanConfig.
    
    I'm not sure if this can be fixed without changes in Swagger, please have a look.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/deki/cxf CXF-7137

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/236.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #236
    
----
commit 9f196443a50c45014ff08a8198cc7fb95532951d
Author: Dennis Kieselhorst <mail@dekies.de>
Date:   2017-02-13T11:49:57Z

    CXF-7137: extended unittest for contact info (working) and security definitions (not working)

----


> 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