[jboss-jira] [JBoss JIRA] (ELY-1100) Configured set-protocol in Elytron Client configuration file is not used

Ondrej Lukas (JIRA) issues at jboss.org
Wed Apr 26 04:52:01 EDT 2017


     [ https://issues.jboss.org/browse/ELY-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Lukas updated ELY-1100:
------------------------------
    Component/s: Authentication Client


> Configured set-protocol in Elytron Client configuration file is not used
> ------------------------------------------------------------------------
>
>                 Key: ELY-1100
>                 URL: https://issues.jboss.org/browse/ELY-1100
>             Project: WildFly Elytron
>          Issue Type: Bug
>          Components: Authentication Client
>    Affects Versions: 1.1.0.Beta34
>            Reporter: Ondrej Lukas
>            Assignee: Darran Lofthouse
>            Priority: Blocker
>
> When some configuration in Elytron Client configuration file uses set-protocol then value of this element is not used for outgoing connection. Elements set-host and set-port are used correctly.
> Following authentication configuration part of wildfly-config.xml should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{set-protocol}} is not used:
> {code}
> <authentication-configurations>
>     <configuration name="auth-config">
>         <set-user-name name="user"/>
>         <set-protocol name="remote+http"/>
>         <set-host name="localhost"/>
>         <set-port number="9990"/>
>         <credentials>
>             <clear-password password="password"/>
>         </credentials>
>     </configuration>
> </authentication-configurations>
> {code}
> We request blocker because this issue blocks feature for RFE EAP7-567. Due to issue incorrect protocol can be unexpectedly used for outgoing connection, e.g. http can be used instead of https.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list