June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6700) MBeanServer.isRegistered() fails when the security manager is enabled

by Derek Horton (JIRA)

Derek Horton created WFLY-6700: ---------------------------------- Summary: MBeanServer.isRegistered() fails when the security manager is enabled Key: WFLY-6700 URL: https://issues.jboss.org/browse/WFLY-6700 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Derek Horton Assignee: Jason Greene Calling MBeanServer.isRegistered() in a servlet fails with the following error when the security manager is enabled: :WFSM000001: Permission check failed (permission "("org.jboss.as.controller.access.rbac.RunAsRolePermission" "org.jboss.as.controller.access.rbac.RunAsRolePermission.SUPERUSER")" in code source "(vfs:/content/SimpleWar.war/WEB-INF/classes <no signer certificates>)" of "null") The code looks like the following: final MBeanServer server = ManagementFactory.getPlatformMBeanServer(); final ObjectName mbeanName = new ObjectName("ima.test:type=imaTest"); System.out.println("*** calling MBeanServer.isRegistered() - "+server.isRegistered(mbeanName)); The META-INF/jboss-permissions.xml looks like the following: <?xml version="1.0" encoding="UTF-8"?> <permissions xmlns="http://xmlns.jcp.org/xml/ns/javaee" version="7"> <permission> <class-name>javax.management.MBeanServerPermission</class-name> <name>createMBeanServer</name> </permission> <permission> <class-name>org.jboss.as.controller.access.rbac.RunAsRolePermission</class-name> <name>*</name> </permission> </permissions> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6113) TransactionAttributeMergingProcessor fails when using generics

by James Baxter (JIRA)

[ https://issues.jboss.org/browse/WFLY-6113?page=com.atlassian.jira.plugin.... ] James Baxter commented on WFLY-6113: ------------------------------------ Are you planning a release of 10.0.1.Final? If so is there any chance of this being included? > TransactionAttributeMergingProcessor fails when using generics > -------------------------------------------------------------- > > Key: WFLY-6113 > URL: https://issues.jboss.org/browse/WFLY-6113 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Markus Chur > Assignee: Fedor Gavrilov > Priority: Minor > Attachments: log.txt, reproducer.zip > > > Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-570) HTTP SCRAM (RFC 7804) Authentication Mechanism

by David Lloyd (JIRA)

David Lloyd created ELY-570: ------------------------------- Summary: HTTP SCRAM (RFC 7804) Authentication Mechanism Key: ELY-570 URL: https://issues.jboss.org/browse/ELY-570 Project: WildFly Elytron Issue Type: Feature Request Components: Authentication Mechanisms, HTTP Reporter: David Lloyd Use the centralized SCRAM mechanism logic to implement the HTTP SCRAM mechanism. For more information see: https://tools.ietf.org/html/rfc7804 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1587) Register runtime attributes depending on the actual type of process/running mode.

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1587?page=com.atlassian.jira.plugi... ] Jeff Mesnil closed WFCORE-1587. ------------------------------- Resolution: Duplicate Issue > Register runtime attributes depending on the actual type of process/running mode. > --------------------------------------------------------------------------------- > > Key: WFCORE-1587 > URL: https://issues.jboss.org/browse/WFCORE-1587 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.1.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > Following work done on WFCORE-1513, runtime operations should also be actually registered if it makes sense (as determined by the ProcessType/RunningMode). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6680) :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6680?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6680: --------------------------------- Summary: :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable (was: :read-proxies-configuration and :read-proxies-info fail when there is no httpd) > :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-6680 > URL: https://issues.jboss.org/browse/WFLY-6680 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Aaron Ogburn > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6682) Upgrade Hibernate to 5.2.0

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6682?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-6682: ------------------------------------ Thanks Frank, great feedback and pull request as well! You already saw my comments on the pull request, questioning whether Hibernate ORM 5.2, would break application compatibility with Hibernate ORM 5.0, due to changes made in 5.2 (like merging hibernate-entity-manager into hibernate-core). [~gbadner] [~epbernard] your feedback is welcome on ^ and/or the https://github.com/wildfly/wildfly/pull/8961 Thanks, Scott > Upgrade Hibernate to 5.2.0 > -------------------------- > > Key: WFLY-6682 > URL: https://issues.jboss.org/browse/WFLY-6682 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Frank Langelage > Assignee: Scott Marlow > Priority: Critical > Fix For: 10.1.0.Final > > > Upgrade Hibernate to latest version 5.2.0.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6699) Custom principal is lost during remote ejb authentication

by Vlado Pakan (JIRA)

Vlado Pakan created WFLY-6699: --------------------------------- Summary: Custom principal is lost during remote ejb authentication Key: WFLY-6699 URL: https://issues.jboss.org/browse/WFLY-6699 Project: WildFly Issue Type: Bug Components: EJB, Security Affects Versions: 10.0.0.Final Reporter: Vlado Pakan Assignee: Vlado Pakan A custom principal (instead of the JBoss provided SimplePrincipal class) is used to store the authenticated username in a custom login module. The custom principal class is lost when attempting to retrieve it from the subject from within a secured EJB. The custom principal is only lost if it is used to store the username instead of using the JBoss provided SimplePrincipal class. Other instances of the custom principal class are passed along successfully if they are storing something besides the username (SSN, CustomerID, etc). It looks like this is happening due to a change (introduced in 6.4.6) in the org.jboss.as.security.service.SimpleSecurityManager.authenticate method @@ -445,8 +408,11 @@ public class SimpleSecurityManager implements ServerSecurityManager { auditPrincipal = unauthenticatedIdentity.asPrincipal(); subject.getPrincipals().add(auditPrincipal); authenticated = true; + } else { + subject.getPrincipals().add(principal); } This change was associated with bz-921217. This only happens when the EJB is accessed from a remote standalone client. If the EJB is accessed from a secured web app (locally), then the custom principal is not lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6680) :read-proxies-configuration and :read-proxies-info fail when there is no httpd

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6680?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6680: -------------------------------------- Just to clarify the problem, it happens when there is at least one working proxy and at least one incorrect proxy. Also this is what the exception is in WF10: {noformat} [standalone@localhost:9990 /] /subsystem=modcluster/:read-proxies-info { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: newValue is null", "rolled-back" => true } [standalone@localhost:9990 /] /subsystem=modcluster/:read-proxies-configuration { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: newValue is null", "rolled-back" => true } {noformat} > :read-proxies-configuration and :read-proxies-info fail when there is no httpd > ------------------------------------------------------------------------------ > > Key: WFLY-6680 > URL: https://issues.jboss.org/browse/WFLY-6680 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Aaron Ogburn > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1589) Upgrade to WildFly Common 1.2.0.Beta1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1589?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1589: ------------------------------------- Labels: affects_elytron (was: ) > Upgrade to WildFly Common 1.2.0.Beta1 > ------------------------------------- > > Key: WFCORE-1589 > URL: https://issues.jboss.org/browse/WFCORE-1589 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: affects_elytron > Fix For: 3.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6682) Upgrade Hibernate to 5.2.0

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-6682?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-6682: --------------------------------------- I'm especially interested in using the new Java 8 datatypes for date and time in my project for the next release as they are now part of the core system and fully supported. I created a pull request. This replaces hibernate 5.0.9 with 5.2.0, the so far named hibernate 5.0.x module is no longer a 5.0.x module but a 5.x module. > Upgrade Hibernate to 5.2.0 > -------------------------- > > Key: WFLY-6682 > URL: https://issues.jboss.org/browse/WFLY-6682 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Frank Langelage > Assignee: Scott Marlow > Priority: Critical > Fix For: 10.1.0.Final > > > Upgrade Hibernate to latest version 5.2.0.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 June 2016