July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1644) PersistenceResourceXmlDescription marshals attributes in the reverse order they are added

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1644?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1644: ------------------------------------- Description: This in marshalAttributes results in iterating over a reversed list: {code} //we sort attributes to make sure that attributes that marshall to elements are last for (AttributeDefinition ad : attributes.stream().sorted((o1, o2) -> o1.getParser().isParseAsElement() ? 1 : -1).collect(Collectors.toList())) { {code} The sorter returning -1 for all non-element attributes has that effect. was: This in marshalAttributes results in iterating over a reversed list: {code} //we sort attributes to make sure that attributes that marshall to elements are last for (AttributeDefinition ad : attributes.stream().sorted((o1, o2) -> o1.getParser().isParseAsElement() ? 1 : -1).collect(Collectors.toList())) { {code} The sorter returning -1 for all non-element attributes has that effect. > PersistenceResourceXmlDescription marshals attributes in the reverse order they are added > ----------------------------------------------------------------------------------------- > > Key: WFCORE-1644 > URL: https://issues.jboss.org/browse/WFCORE-1644 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.2.0.CR5, 3.0.0.Alpha3 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.2.0.CR6, 3.0.0.Alpha4 > > > This in marshalAttributes results in iterating over a reversed list: > {code} > //we sort attributes to make sure that attributes that marshall to elements are last > for (AttributeDefinition ad : attributes.stream().sorted((o1, o2) -> o1.getParser().isParseAsElement() ? 1 : -1).collect(Collectors.toList())) { > {code} > The sorter returning -1 for all non-element attributes has that effect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-586) Evidence check to TokenSecurityRealm

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-586?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-586: --------------------------- Description: We must check the presence of an evidence prior to obtaining it from the {{IdentityLocator}}. Failing to do so, an exception is during authorization. (was: We must check the presence of an evidence prior to obtaining it from the {{IdentityLocator}}.) > Evidence check to TokenSecurityRealm > ------------------------------------ > > Key: ELY-586 > URL: https://issues.jboss.org/browse/ELY-586 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Realms > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > We must check the presence of an evidence prior to obtaining it from the {{IdentityLocator}}. Failing to do so, an exception is during authorization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-586) Evidence check to TokenSecurityRealm

by Pedro Igor (JIRA)

Pedro Igor created ELY-586: ------------------------------ Summary: Evidence check to TokenSecurityRealm Key: ELY-586 URL: https://issues.jboss.org/browse/ELY-586 Project: WildFly Elytron Issue Type: Enhancement Components: Realms Affects Versions: 1.0.2.Final Reporter: Pedro Igor Assignee: Pedro Igor We must check the presence of an evidence prior to obtaining it from the {{IdentityLocator}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-585) Allow null authenticationID during authorization

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-585?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-585: --------------------------- Description: We must be able to support a null authenticationID when using an {{AuthorizeCallback}}. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. (was: We must be support a null authenticationID when using an {{AuthorizeCallback}}. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. ) > Allow null authenticationID during authorization > ------------------------------------------------ > > Key: ELY-585 > URL: https://issues.jboss.org/browse/ELY-585 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Callbacks > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > We must be able to support a null authenticationID when using an {{AuthorizeCallback}}. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-585) Allow null authenticationID during authorization

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-585?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-585: --------------------------- Description: We must be able to support a null authenticationID when using an {{AuthorizeCallback}} to perform authorization. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. (was: We must be able to support a null authenticationID when using an {{AuthorizeCallback}}. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. ) > Allow null authenticationID during authorization > ------------------------------------------------ > > Key: ELY-585 > URL: https://issues.jboss.org/browse/ELY-585 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Callbacks > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > We must be able to support a null authenticationID when using an {{AuthorizeCallback}} to perform authorization. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-585) Allow null authenticationID during authorization

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-585?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-585: --------------------------- Description: We must be able to support a null authenticationID when using an {{AuthorizeCallback}} to perform authorization. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform the authorization. (was: We must be able to support a null authenticationID when using an {{AuthorizeCallback}} to perform authorization. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. ) > Allow null authenticationID during authorization > ------------------------------------------------ > > Key: ELY-585 > URL: https://issues.jboss.org/browse/ELY-585 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Callbacks > Affects Versions: 1.0.2.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > We must be able to support a null authenticationID when using an {{AuthorizeCallback}} to perform authorization. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform the authorization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-585) Allow null authenticationID during authorization

by Pedro Igor (JIRA)

Pedro Igor created ELY-585: ------------------------------ Summary: Allow null authenticationID during authorization Key: ELY-585 URL: https://issues.jboss.org/browse/ELY-585 Project: WildFly Elytron Issue Type: Enhancement Components: Callbacks Affects Versions: 1.0.2.Final Reporter: Pedro Igor Assignee: Pedro Igor We must be support a null authenticationID when using an {{AuthorizeCallback}}. In this case, if an authenticated principal was previously established as a result of a successful authentication or evidence verification, we just use it to perform authorization. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1523) RestartParentResourceRemoveHandler should fail when removing non-existing resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1523?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1523: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1543, https://github.com/wildfly/wildfly-core/pull/1657, https://github.com/wildfly/wildfly-core/pull/1658 (was: https://github.com/wildfly/wildfly/pull/8896, https://github.com/wildfly/wildfly-core/pull/1543) > RestartParentResourceRemoveHandler should fail when removing non-existing resources > ----------------------------------------------------------------------------------- > > Key: WFCORE-1523 > URL: https://issues.jboss.org/browse/WFCORE-1523 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Priority: Minor > Labels: 2.2 > Fix For: 3.0.0.Alpha1, 2.2.0.CR6 > > > In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1326) naming.xml : the LookupPool bean should have a destroy element

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1326?page=com.atlassian.jira.plugin... ] Stefano Maestri resolved JBJCA-1326. ------------------------------------ Resolution: Done https://github.com/ironjacamar/ironjacamar/commit/76d07d21e97eae656246f21... > naming.xml : the LookupPool bean should have a destroy element > -------------------------------------------------------------- > > Key: JBJCA-1326 > URL: https://issues.jboss.org/browse/JBJCA-1326 > Project: IronJacamar > Issue Type: Bug > Components: Embedded > Affects Versions: WildFly/IronJacamar 1.3.4.Final, 1.2.7.Final > Reporter: Alexis Hassler > Assignee: Stefano Maestri > Priority: Minor > Fix For: 1.2.8.Final, master > > > IronJacamar Embedded does not shutdown properly because of the lack of destroy element. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1643) Fix domain mode for configuration changes

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1643: ---------------------------------------- Summary: Fix domain mode for configuration changes Key: WFCORE-1643 URL: https://issues.jboss.org/browse/WFCORE-1643 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha3 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet The configuration changes feature is broken in domain mode: the propagation to managed servers / slaves HC doesn't work properly. Once set it will fail on restarting the DC. So we need a clean refactoring of the feature to have a usable domain mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016