August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-54: ----------------------------------- Fix Version/s: 1.0.0.Alpha6 (was: 1.0.0.Alpha5) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.Alpha6 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-42) Add a ServerXml Parser which extends CommonXml

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-42?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-42: ----------------------------------- Fix Version/s: 1.0.0.Alpha6 (was: 1.0.0.Alpha5) > Add a ServerXml Parser which extends CommonXml > ---------------------------------------------- > > Key: WFCORE-42 > URL: https://issues.jboss.org/browse/WFCORE-42 > Project: WildFly Core > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha6 > > > Both StandaloneXml and AppclientXml parse XML starting from the server element. > This duplication has always been problematic as AppclientXml is completely separate from the remaining domain config parsing, however with the core split this is even worse. > This change is to introduce a ServerXml that can be the common base for both StandaloneXml and AppclientXml - except in extreme cases it will then be safe to ignore AppclientXml for further schema updates. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-71) ProtocolLogger is used outside org.jboss.as.protocol module but isn't available

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-71: -------------------------------------- Summary: ProtocolLogger is used outside org.jboss.as.protocol module but isn't available Key: WFCORE-71 URL: https://issues.jboss.org/browse/WFCORE-71 Project: WildFly Core Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 1.0.0.Alpha5 Reporter: Brian Stansberry Assignee: Brian Stansberry The ProtocolLogger class is used in a few places in host-controller and server, but the module.xml for the org.jboss.as.protocol module specifically excludes it from being exported. The uses aren't complex enough to justify exporting the class, so I'll just change them. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3776) ClassNotFound exception when running Arquillian test

by xiaodong xie (JIRA)

xiaodong xie created WFLY-3776: ---------------------------------- Summary: ClassNotFound exception when running Arquillian test Key: WFLY-3776 URL: https://issues.jboss.org/browse/WFLY-3776 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.1.0.Final Environment: Mac Reporter: xiaodong xie Assignee: Jason Greene org.jboss.as.embedded.EmbeddedStandAloneServerFactory uses org.jboss.as.protocol.StreamUtils, which belongs to "org.jboss.as.protocol" module. This module is not imported in "org.jboss.as.embedded" module. Adding the import fix the issue. Thanks. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-457) Replace mod_cluster proxy-list attribute with list of outbound socket bindings

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-457?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated WFLY-457: -------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 9.0.0.CR1) > Replace mod_cluster proxy-list attribute with list of outbound socket bindings > ------------------------------------------------------------------------------ > > Key: WFLY-457 > URL: https://issues.jboss.org/browse/WFLY-457 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Currently, the mod_cluster subsystem defines proxies using a comma separated string of address:port. This attribute needs to be deprecated in favor of an attribute, call it "proxies" that defines an xs:list of outbound socket binding names. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ] David Lloyd commented on ELY-47: -------------------------------- OK good :) I was very worried we'd have to implement normalization ourselves - something that I dread :) > NFKC normalization in StringPrep is not in accordance with RFC > -------------------------------------------------------------- > > Key: ELY-47 > URL: https://issues.jboss.org/browse/ELY-47 > Project: WildFly Elytron > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jan Kalina > Assignee: Darran Lofthouse > > StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table: > http://tools.ietf.org/html/rfc3454#appendix-B.2 > Relevant profile description: > http://tools.ietf.org/html/rfc3454#section-3.2 > Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing can be used this simple test: > {code:java} > @Test > public void testNormalizationWithNFKC(){ > ByteStringBuilder b = new ByteStringBuilder(); > String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047"; > String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067"; > StringPrep.encode(before, b, StringPrep.NORMALIZE_KC); > assertEquals(after, new String(b.toArray())); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ] Jan Kalina commented on ELY-47: ------------------------------- No, I created new test and I understood wrong meaning of NORMALIZE_KC profile. This profile correctly do NFKC normalization, but I think it should do also case folding. (I overlooked "4. Normalization" and found KC normalization only in "3.2 Case folding" in RFC) StringPrep in OK (except other problems fixed in pull request 13), only my test (part of same pull request) was wrong (also fixed). Thread can be closed. > NFKC normalization in StringPrep is not in accordance with RFC > -------------------------------------------------------------- > > Key: ELY-47 > URL: https://issues.jboss.org/browse/ELY-47 > Project: WildFly Elytron > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jan Kalina > Assignee: Darran Lofthouse > > StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table: > http://tools.ietf.org/html/rfc3454#appendix-B.2 > Relevant profile description: > http://tools.ietf.org/html/rfc3454#section-3.2 > Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing can be used this simple test: > {code:java} > @Test > public void testNormalizationWithNFKC(){ > ByteStringBuilder b = new ByteStringBuilder(); > String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047"; > String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067"; > StringPrep.encode(before, b, StringPrep.NORMALIZE_KC); > assertEquals(after, new String(b.toArray())); > } > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-70) Revisit redirect tests in HTTPSManagementInterfaceTestCase

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-70: -------------------------------------- Summary: Revisit redirect tests in HTTPSManagementInterfaceTestCase Key: WFCORE-70 URL: https://issues.jboss.org/browse/WFCORE-70 Project: WildFly Core Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management, Test Suite Reporter: Brian Stansberry See discussion at https://github.com/wildfly/wildfly-core/pull/120 HTTPSManagementInterfaceTestCase includes tests of how http/https redirects are handled by the http interface logic. But it seems that every time some variant of SSLException is thrown, which largely defeats the point of the tests. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3775) @TransactionAttribute ignored on non-public methods.

by Sławomir Wojtasiak (JIRA)

Sławomir Wojtasiak created WFLY-3775: ---------------------------------------- Summary: @TransactionAttribute ignored on non-public methods. Key: WFLY-3775 URL: https://issues.jboss.org/browse/WFLY-3775 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 8.1.0.Final Environment: SunOS, JDK1.7. Reporter: Sławomir Wojtasiak Assignee: David Lloyd Priority: Minor Currently @TransactionAttribute annotations are allowed only on public methods. It seems to be a reasonable rule because components are accesses by their public interfaces and session beans can be also accessed by a no-interface view that exposes all public methods of the bean class. Nevertheless in case of singletons @PostConstruct and @PreDestroy annotations can be applied to protected methods for instance. In such a case transaction attributes are silently ignored. (org.jboss.as.ejb3.component.EJBComponentCreateService:147) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3269) XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3269: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1133961|https://bugzilla.redhat.com/show_bug.cgi?id=1133961] from ASSIGNED to POST > XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value. > ------------------------------------------------------------------------------------------------- > > Key: WFLY-3269 > URL: https://issues.jboss.org/browse/WFLY-3269 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.Beta1 > > > {code} > Trying so, I run in the error (when starting WildFly) : > 10:28:29,674 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[76,25] > Message: JBAS014724: Missing required attribute(s): FORCE > at org.jboss.as.controller.parsing.ParseUtils.missingRequired(ParseUtils.java:134) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final] > at org.jboss.as.domain.management.parsing.ManagementXml.parseUsernameToDn_2_0(ManagementXml.java:2118) [wildfly-domain-management-8.0.0.Final.jar:8.0.0.Final] > {code} > {code} > <security-realm name="MgtRealm"> > <authentication> > <ldap connection="ovodavLDAP" base-dn="ou=People,dc=hydrogenic,dc=local"> >  > <username-filter attribute="uid"/> > </ldap> > </authentication> > <authorization> > <ldap connection="ovodavLDAP"> > <username-to-dn> > <username-filter base-dn="ou=People,dc=hydrogenic,dc=local" recursive="false" attribute="uid" user-dn-attribute="dn" /> > </username-to-dn> > <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="uid"> > <group-to-principal base-dn="ou=Groups,dc=hydrogenic,dc=local" recursive="true" search-by="DISTINGUISHED_NAME"> > <membership-filter principal-attribute="uniqueMember" /> > </group-to-principal> > </group-search> > </ldap> > </authorization> > </security-realm> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 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 August 2014