April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2724) Attribute protocol in authentication-configuration of Elytron subsystem is not used

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-2724: ------------------------------------ Summary: Attribute protocol in authentication-configuration of Elytron subsystem is not used Key: WFCORE-2724 URL: https://issues.jboss.org/browse/WFCORE-2724 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Blocker When authentication-configuration in Elytron subsystem uses attribute {{protocol}} then value of this attribute is not used for outgoing connection. Attributes {{host}} and {{port}} are used correctly. Following authentication-configuration of Elytron subsystem should use URL {{remote+http://localhost:9990}} for outgoing connection, but protocol {{remote+http}} from {{protocol}} is not used: {code} <authentication-configuration name="authConfig" authentication-name="admin" protocol="remote+http" host="localhost" port="9990"> <credential-reference clear-text="pass@123"/> </authentication-configuration> {code} We request blocker because this issue blocks feature for RFE EAP7-568. Due to issue incorrect protocol can be unexpectedly used for outgoing connection, e.g. http can be used instead of https. This issue is blocker for GA, not for testing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1101) Elytron FIPS CS, javax.crypto.BadPaddingException

by Peter Skopek (JIRA)

Peter Skopek created ELY-1101: --------------------------------- Summary: Elytron FIPS CS, javax.crypto.BadPaddingException Key: ELY-1101 URL: https://issues.jboss.org/browse/ELY-1101 Project: WildFly Elytron Issue Type: Bug Components: Credential Store Affects Versions: 1.1.0.Beta38 Reporter: Peter Skopek Assignee: Peter Skopek Wrong offset causing padding check to throw BadPaddingException. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1100?page=com.atlassian.jira.plugin.s... ] 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)

9 years

1
0
0 / 0

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

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1100?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1100: ------------------------------ Description: 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} was: 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. > 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} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-1100?page=com.atlassian.jira.plugin.s... ] Ondrej Lukas updated ELY-1100: ------------------------------ Affects Version/s: 1.1.0.Beta34 > 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)

9 years

1
0
0 / 0

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

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-1100: --------------------------------- Summary: 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 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)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8641) rewrite handler produces invalid URLs when used with query part

by Markus Stier (JIRA)

[ https://issues.jboss.org/browse/WFLY-8641?page=com.atlassian.jira.plugin.... ] Markus Stier updated WFLY-8641: ------------------------------- Steps to Reproduce: Undertow configuration (relevant parts only): {code} <subsystem xmlns="urn:jboss:domain:undertow:3.1"> <buffer-cache name="default"/> <server name="default-server"> <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/> <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/> <host name="default-host" alias="localhost, home"> <access-log pattern="Def: %h %t %v "%r" %s " use-server-log="true"/> <filter-ref name="to-query0" predicate="regex('^/?$') and equals(%{LOCAL_SERVER_NAME}, 'home:8180')"/> </host> </server> <filters> <rewrite name="to-query0" target="/somepath?param=1234"/> <expression-filter name="to-query1" expression="rewrite('/somepath?param=1234')"/> <expression-filter name="to-query2" expression="rewrite('/somepath'); set(attribute='%{q,param}', value='1234')"/> <expression-filter name="to-query3" expression="rewrite('/somepath'); set(attribute='%{QUERY_STRING}', value='param=1234')"/> <expression-filter name="to-query4" expression="set(attribute='%{RELATIVE_PATH}', value='/somepath'); set(attribute='%{QUERY_STRING}', value='param=1234')"/> </filters> </subsystem> {code} Results of the different filters: {code} // erroneous to-query0: /somepath?param=1234??param=1234 to-query1: /somepath?param=1234??param=1234 to-query2: /somepath // as expected to-query3: /somepath?param=1234 to-query4: /somepath?param=1234 {code} was: Undertow configuration (relevant parts only): {code} <subsystem xmlns="urn:jboss:domain:undertow:3.1"> <buffer-cache name="default"/> <server name="default-server"> <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/> <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/> <host name="default-host" alias="localhost, documents, home, eaptest.rssystem.de"> <access-log pattern="Def: %h %t %v "%r" %s " use-server-log="true"/> <filter-ref name="to-query0" predicate="regex('^/?$') and equals(%{LOCAL_SERVER_NAME}, 'home:8180')"/> </host> </server> <filters> <rewrite name="to-query0" target="/somepath?param=1234"/> <expression-filter name="to-query1" expression="rewrite('/somepath?param=1234')"/> <expression-filter name="to-query2" expression="rewrite('/somepath'); set(attribute='%{q,param}', value='1234')"/> <expression-filter name="to-query3" expression="rewrite('/somepath'); set(attribute='%{QUERY_STRING}', value='param=1234')"/> <expression-filter name="to-query4" expression="set(attribute='%{RELATIVE_PATH}', value='/somepath'); set(attribute='%{QUERY_STRING}', value='param=1234')"/> </filters> </subsystem> {code} Results of the different filters: {code} // erroneous to-query0: /somepath?param=1234??param=1234 to-query1: /somepath?param=1234??param=1234 to-query2: /somepath // as expected to-query3: /somepath?param=1234 to-query4: /somepath?param=1234 {code} > rewrite handler produces invalid URLs when used with query part > --------------------------------------------------------------- > > Key: WFLY-8641 > URL: https://issues.jboss.org/browse/WFLY-8641 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: * Windows 10 > * Wildfly 10.1.0 Final > Reporter: Markus Stier > Assignee: Stuart Douglas > > Context: > a request of the form "http://home:8180/" should be rewritten to "http://home:8180/somepath?param=1234" > Problem: > The rewrite handler produces URLs which contain duplicated query parts and question marks. See excerpt from access log below. > {code} > [26/Apr/2017:09:26:09 +0200] home:8180 "GET /somepath?param=1234??param=1234 HTTP/1.1" 404 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8641) rewrite handler produces invalid URLs when used with query part

by Markus Stier (JIRA)

Markus Stier created WFLY-8641: ---------------------------------- Summary: rewrite handler produces invalid URLs when used with query part Key: WFLY-8641 URL: https://issues.jboss.org/browse/WFLY-8641 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 10.1.0.Final Environment: * Windows 10 * Wildfly 10.1.0 Final Reporter: Markus Stier Assignee: Stuart Douglas Context: a request of the form "http://home:8180/" should be rewritten to "http://home:8180/somepath?param=1234" Problem: The rewrite handler produces URLs which contain duplicated query parts and question marks. See excerpt from access log below. {code} [26/Apr/2017:09:26:09 +0200] home:8180 "GET /somepath?param=1234??param=1234 HTTP/1.1" 404 {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2715) principal and authentication-context in Elytron dir-context should be mutually exclusive

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2715?page=com.atlassian.jira.plugi... ] Chao Wang reassigned WFCORE-2715: --------------------------------- Assignee: Chao Wang (was: Darran Lofthouse) > principal and authentication-context in Elytron dir-context should be mutually exclusive > ---------------------------------------------------------------------------------------- > > Key: WFCORE-2715 > URL: https://issues.jboss.org/browse/WFCORE-2715 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta13 > Reporter: Ondrej Lukas > Assignee: Chao Wang > Priority: Critical > > To avoid possibility when two different principals are configured in Elytron dir-context, its attributes {{principal}} and {{authentication-context}} should be mutually exclusive. > It is similar issue as WFCORE-2396. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8640) Implementation version does not correspond to JAR version for wildfly-client-all src JAR

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/WFLY-8640?page=com.atlassian.jira.plugin.... ] Petr Sakař commented on WFLY-8640: ---------------------------------- Issue is caused by missing commit for JBEAP-1185 > Implementation version does not correspond to JAR version for wildfly-client-all src JAR > ---------------------------------------------------------------------------------------- > > Key: WFLY-8640 > URL: https://issues.jboss.org/browse/WFLY-8640 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Petr Sakař > Assignee: Petr Sakař > > The affected JAR: wildfly-client-all-VERSION-sources.jar > Currently > Manifest contains: {{Implementation version: WRONG_VERSION}} > Should be > Manifest contains: {{Implementation version: VERSION}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017