[JBoss JIRA] (ELY-1348) LegacyPropertiesRealm should use spec passed into getCredential
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1348?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1348:
----------------------------
Description: As suggested in JBEAP-8700 comments, when DIGEST mechanism and plain-text properties realm used, realm should use digest realm name from HTTP mechanism - which is already passed into getCredential method but ignored by properties-realm yet. (was: There should be a possibility to retrieve additional information (e.g. Digest Realm name) in the realms when calling {{getCredential}} method. Currently such info has to be provided (duplicated) in the realm configuration.
This issue is created as follow up for JBEAP-6003. See [this comment|https://issues.jboss.org/browse/JBEAP-6003?focusedCommentId=13359...] with HipChat discussion.
)
> LegacyPropertiesRealm should use spec passed into getCredential
> ---------------------------------------------------------------
>
> Key: ELY-1348
> URL: https://issues.jboss.org/browse/ELY-1348
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Realms
> Affects Versions: 1.2.0.Beta1
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Labels: security-realm
>
> As suggested in JBEAP-8700 comments, when DIGEST mechanism and plain-text properties realm used, realm should use digest realm name from HTTP mechanism - which is already passed into getCredential method but ignored by properties-realm yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (JGRP-2061) TYPE_STRING does not handle unicode
by Cody Ebberson (JIRA)
[ https://issues.jboss.org/browse/JGRP-2061?page=com.atlassian.jira.plugin.... ]
Cody Ebberson commented on JGRP-2061:
-------------------------------------
Confirmed, this works for me. Appears fixed. Thanks!
> TYPE_STRING does not handle unicode
> -----------------------------------
>
> Key: JGRP-2061
> URL: https://issues.jboss.org/browse/JGRP-2061
> Project: JGroups
> Issue Type: Bug
> Reporter: Cody Ebberson
> Assignee: Bela Ban
> Fix For: 4.0.6
>
>
> In several places throughout the org.jgroups.util.Util class, it is assumed that Strings are one byte per character.
> For example, see objectToByteBuffer lines 561-567:
> https://github.com/belaban/JGroups/blob/master/src/org/jgroups/util/Util....
> {code:java}
> case TYPE_STRING:
> String str=(String)obj;
> int len=str.length();
> ByteBuffer retval=ByteBuffer.allocate(Global.BYTE_SIZE + len).put(TYPE_STRING);
> for(int i=0; i < len; i++)
> retval.put((byte)str.charAt(i));
> return retval.array();
> {code}
> This code will incorrectly encode any String with non ASCII encoding.
> There are several options to fix. You could use str.getBytes(StandardCharsets.UTF_8) to get a proper byte encoding, or you could use the existing TYPE_SERIALIZABLE code path.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFLY-9240) WeldSecurityServices not able to obtain the current SecurityDomain anymore
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ]
Martin Kouba updated WFLY-9240:
-------------------------------
Description:
The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.
Note that this worked on WildFly *11.0.0.Alpha1*.
It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated.
was:
The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.
Note that this worked on WildFly 11.0.0.Alpha1.
It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated.
> WeldSecurityServices not able to obtain the current SecurityDomain anymore
> --------------------------------------------------------------------------
>
> Key: WFLY-9240
> URL: https://issues.jboss.org/browse/WFLY-9240
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Security
> Affects Versions: 11.0.0.Beta1, 11.0.0.CR1
> Reporter: Martin Kouba
> Assignee: Darran Lofthouse
> Priority: Critical
>
> The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
> The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.
> Note that this worked on WildFly *11.0.0.Alpha1*.
> It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFLY-9240) WeldSecurityServices not able to obtain the current SecurityDomain anymore
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ]
Martin Kouba updated WFLY-9240:
-------------------------------
Steps to Reproduce:
# clone Weld WildFly fork and build the project
# clone Weld repo, build the project and run {{org.jboss.weld.tests.event.async.context.security.SecurityContextPropagationTest}}
{noformat}
$ git clone -b 11.0.0.CR1-weld3 git@github.com:weld/wildfly.git
$ cd wildfly
$ mvn clean install -DskipTests
$ cd ../
$ git clone git@github.com:weld/core.git
$ cd core
$ mvn clean install -DskipTests
$ export JBOSS_HOME=WFLYREPO/dist/target/wildfly-11.0.0.Beta1
$ mvn clean test -Dincontainer -Dtest=SecurityContextPropagationTest -f tests-arquillian/pom.xml
{noformat}
was:
# clone Weld WildFly fork and build the project
# clone Weld repo, build the project and run {{org.jboss.weld.tests.event.async.context.security.SecurityContextPropagationTest}}
{noformat}
$ git clone -b 11.0.0.Beta1-weld3 git@github.com:weld/wildfly.git
$ cd wildfly
$ mvn clean install -DskipTests
$ cd ../
$ git clone git@github.com:weld/core.git
$ cd core
$ mvn clean install -DskipTests
$ export JBOSS_HOME=WFLYREPO/dist/target/wildfly-11.0.0.Beta1
$ mvn clean test -Dincontainer -Dtest=SecurityContextPropagationTest -f tests-arquillian/pom.xml
{noformat}
> WeldSecurityServices not able to obtain the current SecurityDomain anymore
> --------------------------------------------------------------------------
>
> Key: WFLY-9240
> URL: https://issues.jboss.org/browse/WFLY-9240
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Security
> Affects Versions: 11.0.0.Beta1, 11.0.0.CR1
> Reporter: Martin Kouba
> Assignee: Darran Lofthouse
> Priority: Critical
>
> The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
> The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.
> Note that this worked on WildFly 11.0.0.Alpha1.
> It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months
[JBoss JIRA] (WFLY-9240) WeldSecurityServices not able to obtain the current SecurityDomain anymore
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9240?page=com.atlassian.jira.plugin.... ]
Martin Kouba updated WFLY-9240:
-------------------------------
Steps to Reproduce:
# clone Weld WildFly fork and build the project
# clone Weld repo, build the project and run {{org.jboss.weld.tests.event.async.context.security.SecurityContextPropagationTest}}
{noformat}
$ git clone -b 11.0.0.Beta1-weld3 git@github.com:weld/wildfly.git
$ cd wildfly
$ mvn clean install -DskipTests
$ cd ../
$ git clone git@github.com:weld/core.git
$ cd core
$ mvn clean install -DskipTests
$ export JBOSS_HOME=WFLYREPO/dist/target/wildfly-11.0.0.Beta1
$ mvn clean test -Dincontainer -Dtest=SecurityContextPropagationTest -f tests-arquillian/pom.xml
{noformat}
was:
* clone Weld WildFly fork ({{git clone -b 11.0.0.Beta1-weld3 git@github.com:weld/wildfly.git}}) and build the project ({{mvn clean install -DskipTests}})
* clone Weld repo ({{git clone git@github.com:weld/core.git}}) and run {{org.jboss.weld.tests.event.async.context.security.SecurityContextPropagationTest}}:
## {{export JBOSS_HOME=WFLYREPO/dist/target/wildfly-11.0.0.Beta1}}
## {{mvn clean test -Dincontainer -Dtest=SecurityContextPropagationTest -f tests-arquillian/pom.xml}}
> WeldSecurityServices not able to obtain the current SecurityDomain anymore
> --------------------------------------------------------------------------
>
> Key: WFLY-9240
> URL: https://issues.jboss.org/browse/WFLY-9240
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Security
> Affects Versions: 11.0.0.Beta1, 11.0.0.CR1
> Reporter: Martin Kouba
> Assignee: Darran Lofthouse
> Priority: Critical
>
> The integration code used by Weld 3 to propagate the security context of the current thread to different threads (needed for async events CDI 2.0 feature) is not able to obtain the current {{org.wildfly.security.auth.server.SecurityDomain}} anymore.
> The invocation of [SecurityDomain.getCurrent()|https://github.com/weld/wildfly/blob/11.0.0.B...] returns {{null}}.
> Note that this worked on WildFly 11.0.0.Alpha1.
> It's also possible that the test (see also steps to reproduce) is wrong. A review/help from a security expert would be appreciated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 3 months