May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3826) anonymous authentication for ejbs using legacy configuration

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3826?page=com.atlassian.jira.plugi... ] Jiri Ondrusek moved WFLY-10360 to WFCORE-3826: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3826 (was: WFLY-10360) Component/s: Security (was: Security) Affects Version/s: 5.0.0.Alpha7 (was: 13.0.0.Beta1) > anonymous authentication for ejbs using legacy configuration > ------------------------------------------------------------ > > Key: WFCORE-3826 > URL: https://issues.jboss.org/browse/WFCORE-3826 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration: > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> > <properties> > <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > </properties> > </http-connector> > </subsystem> > Unfortunately, this same configuration does not work on 7.1.1. It looks > like the server still wants to use DIGEST-MD5 based authentication. > Has the legacy based configuration (non-elytron) for anonymous ejb > access changed on eap 7.1.1? > I am attaching the standalone.xml, server.log and client log. > Customer does not want to use elytron at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10360) anonymous authentication for ejbs using legacy configuration

by Jiri Ondrusek (JIRA)

Jiri Ondrusek created WFLY-10360: ------------------------------------ Summary: anonymous authentication for ejbs using legacy configuration Key: WFLY-10360 URL: https://issues.jboss.org/browse/WFLY-10360 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 13.0.0.Beta1 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration: <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <endpoint/> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> <properties> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/> <property name="SASL_POLICY_NOANONYMOUS" value="false"/> </properties> </http-connector> </subsystem> Unfortunately, this same configuration does not work on 7.1.1. It looks like the server still wants to use DIGEST-MD5 based authentication. Has the legacy based configuration (non-elytron) for anonymous ejb access changed on eap 7.1.1? I am attaching the standalone.xml, server.log and client log. Customer does not want to use elytron at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1579) Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/ELY-1579?page=com.atlassian.jira.plugin.s... ] Jiri Ondrusek moved WFLY-10359 to ELY-1579: ------------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-1579 (was: WFLY-10359) Component/s: Authentication Mechanisms (was: Security) Affects Version/s: 1.3.1.Final (was: 13.0.0.Beta1) > Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353 > --------------------------------------------------------------------------------------------------------- > > Key: ELY-1579 > URL: https://issues.jboss.org/browse/ELY-1579 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.3.1.Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > See https://issues.jboss.org/browse/WFLY-10353. > To solve this fix, there has to be support of delayed definition of mechanisms in SortedMechanismSaslServerFactory -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10359) Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFLY-10359?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-10359: --------------------------------- Description: See https://issues.jboss.org/browse/WFLY-10353. To solve this fix, there has to be support of delayed definition of mechanisms in SortedMechanismSaslServerFactory was: Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration: <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <endpoint/> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> <properties> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/> <property name="SASL_POLICY_NOANONYMOUS" value="false"/> </properties> </http-connector> </subsystem> Unfortunately, this same configuration does not work on 7.1.1. It looks like the server still wants to use DIGEST-MD5 based authentication. Has the legacy based configuration (non-elytron) for anonymous ejb access changed on eap 7.1.1? I am attaching the standalone.xml, server.log and client log. Customer does not want to use elytron at the moment. > Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353 > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-10359 > URL: https://issues.jboss.org/browse/WFLY-10359 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta1 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > See https://issues.jboss.org/browse/WFLY-10353. > To solve this fix, there has to be support of delayed definition of mechanisms in SortedMechanismSaslServerFactory -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10359) Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFLY-10359?page=com.atlassian.jira.plugin... ] Jiri Ondrusek updated WFLY-10359: --------------------------------- Summary: Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353 (was: anonymous authentication for ejbs using legacy configuration) > Allow definition of mechanisms in SortedMechanismSaslServerFactory after server is started for WFLY-10353 > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-10359 > URL: https://issues.jboss.org/browse/WFLY-10359 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta1 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration: > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> > <properties> > <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > </properties> > </http-connector> > </subsystem> > Unfortunately, this same configuration does not work on 7.1.1. It looks > like the server still wants to use DIGEST-MD5 based authentication. > Has the legacy based configuration (non-elytron) for anonymous ejb > access changed on eap 7.1.1? > I am attaching the standalone.xml, server.log and client log. > Customer does not want to use elytron at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10359) anonymous authentication for ejbs using legacy configuration

by Jiri Ondrusek (JIRA)

Jiri Ondrusek created WFLY-10359: ------------------------------------ Summary: anonymous authentication for ejbs using legacy configuration Key: WFLY-10359 URL: https://issues.jboss.org/browse/WFLY-10359 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 13.0.0.Beta1 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Anonymous authentication for ejbs works on EAP 7.0.x using the following configuration: <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <endpoint/> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> <properties> <property name="SASL_MECHANISMS" value="ANONYMOUS,PLAIN"/> <property name="SASL_POLICY_NOANONYMOUS" value="false"/> </properties> </http-connector> </subsystem> Unfortunately, this same configuration does not work on 7.1.1. It looks like the server still wants to use DIGEST-MD5 based authentication. Has the legacy based configuration (non-elytron) for anonymous ejb access changed on eap 7.1.1? I am attaching the standalone.xml, server.log and client log. Customer does not want to use elytron at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WFCORE POM contains duplicate version properties after component-matrix version revert

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-3722: ------------------------------ Description: {noformat} $ grep "<version.org.wildfly.build-tools>" `find . -name pom.xml` ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> {noformat} {noformat} $ grep "<version.org.wildfly.checkstyle-config>" `find . -name pom.xml` ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> {noformat} {noformat} $ grep "<version.org.wildfly.plugin>" `find . -name pom.xml` ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> {noformat} was: {noformat} $ grep build-tools `find . -name pom.xml` ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> {noformat} > WFCORE POM contains duplicate version properties after component-matrix version revert > -------------------------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 5.0.0.Alpha7 > Reporter: David Lloyd > Assignee: Chao Wang > > {noformat} > $ grep "<version.org.wildfly.build-tools>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.10.Final</version.org.wildfly.build-tools> > {noformat} > {noformat} > $ grep "<version.org.wildfly.checkstyle-config>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> > ./pom.xml: <version.org.wildfly.checkstyle-config>1.0.5.Final</version.org.wildfly.checkstyle-config> > {noformat} > {noformat} > $ grep "<version.org.wildfly.plugin>" `find . -name pom.xml` > ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> > ./pom.xml: <version.org.wildfly.plugin>1.2.0.Final</version.org.wildfly.plugin> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WFCORE POM contains duplicate version properties after component-matrix version revert

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-3722: ------------------------------ Summary: WFCORE POM contains duplicate version properties after component-matrix version revert (was: WildFly Build Tools version properties is set in two different POMs) > WFCORE POM contains duplicate version properties after component-matrix version revert > -------------------------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 5.0.0.Alpha7 > Reporter: David Lloyd > Assignee: Chao Wang > > {noformat} > $ grep build-tools `find . -name pom.xml` > ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WFCORE POM contains duplicate version properties after component-matrix version revert

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] Chao Wang updated WFCORE-3722: ------------------------------ Affects Version/s: 5.0.0.Alpha7 > WFCORE POM contains duplicate version properties after component-matrix version revert > -------------------------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 5.0.0.Alpha7 > Reporter: David Lloyd > Assignee: Chao Wang > > {noformat} > $ grep build-tools `find . -name pom.xml` > ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3825) Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers)

by Marek Kopecký (JIRA)

Marek Kopecký created WFCORE-3825: ------------------------------------- Summary: Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) Key: WFCORE-3825 URL: https://issues.jboss.org/browse/WFCORE-3825 Project: WildFly Core Issue Type: Bug Components: Scripts Reporter: Marek Kopecký Assignee: Kabir Khan Unify "-server" option in windows scripts (ps1, bat) for domain mode (and its servers) Domain use "-server" option in unix, windows bat. Domain doesn't use "-server" option in windows ps1 scripts. Same for JVMs of domain servers. I prefer to add "-server" option to ps1 scripts. {noformat:title=domain.ps1 - "-server" option is missing} PS C:\Users\Administrator\playground\wfly.15\wildfly\bin> .\domain.ps1 ================================================================================= JBoss Bootstrap Environment JBOSS_HOME: C:\Users\Administrator\playground\wfly.15\wildfly JAVA: C:\Program Files\Java\jdk1.8.0_121\bin\java.exe MODULE_OPTS: JAVA_OPTS: -Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman ================================================================================= ... {noformat} {noformat:title=domain.bat - "-server" option is listed in JAVA_OPTS} C:\Users\Administrator\playground\wfly.15\wildfly\bin>domain.bat Calling "C:\Users\Administrator\playground\wfly.15\wildfly\bin\domain.conf.bat" Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_121\bin\java" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: "C:\Users\Administrator\playground\wfly.15\wildfly" JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java" JAVA_OPTS: "-Xms64M -Xmx512M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -server" =============================================================================== ... {noformat} cc: [~jamezp] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

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 May 2018