March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6341) Missing testcase for BouncyCastle module usage

by Jan Blizňák (JIRA)

Jan Blizňák created WFLY-6341: --------------------------------- Summary: Missing testcase for BouncyCastle module usage Key: WFLY-6341 URL: https://issues.jboss.org/browse/WFLY-6341 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 10.0.0.Final Reporter: Jan Blizňák Assignee: Jan Blizňák A testcase should be introduced for checking that BouncyCastleProvider from container module can be loaded and used through JCE api. This test is needed to be sure there will be no regression with future version upgrades of BouncyCastle library: missing/incorrect signature in upstream artifact or when running on another JDK that doesn't accept certificate used for signing security providers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6340) Adding deployment permissions doesn't put server in requires reload state

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6340?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-6340: -------------------------------- Assignee: Kabir Khan (was: Tomas Hofman) > Adding deployment permissions doesn't put server in requires reload state > ------------------------------------------------------------------------- > > Key: WFLY-6340 > URL: https://issues.jboss.org/browse/WFLY-6340 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Kabir Khan > Fix For: 10.1.0.Final > > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6340) Adding deployment permissions doesn't put server in requires reload state

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6340?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6340: ----------------------------- Summary: Adding deployment permissions doesn't put server in requires reload state (was: Change in permissions is not visible until server reload) > Adding deployment permissions doesn't put server in requires reload state > ------------------------------------------------------------------------- > > Key: WFLY-6340 > URL: https://issues.jboss.org/browse/WFLY-6340 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Tomas Hofman > Fix For: 10.1.0.Final > > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6340) Change in permissions is not visible until server reload

by Kabir Khan (JIRA)

Kabir Khan created WFLY-6340: -------------------------------- Summary: Change in permissions is not visible until server reload Key: WFLY-6340 URL: https://issues.jboss.org/browse/WFLY-6340 Project: WildFly Issue Type: Bug Components: Security Manager Affects Versions: 10.0.0.Alpha4 Reporter: Josef Cacek Assignee: Tomas Hofman Fix For: 10.0.0.Alpha6 When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6340) Change in permissions is not visible until server reload

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6340?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-6340: ----------------------------- Fix Version/s: 10.1.0.Final (was: 10.0.0.Alpha6) > Change in permissions is not visible until server reload > -------------------------------------------------------- > > Key: WFLY-6340 > URL: https://issues.jboss.org/browse/WFLY-6340 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Tomas Hofman > Fix For: 10.1.0.Final > > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1088) Add spring-jbpm-osgi-example to JBPM repository

by David virgil naranjo (JIRA)

David virgil naranjo created DROOLS-1088: -------------------------------------------- Summary: Add spring-jbpm-osgi-example to JBPM repository Key: DROOLS-1088 URL: https://issues.jboss.org/browse/DROOLS-1088 Project: Drools Issue Type: Feature Request Affects Versions: 6.4.0.CR1 Reporter: David virgil naranjo Assignee: Petr Široký The spring-jbpm-osgi-example is currently placed on Fuse-bxms-integ repository. It will be removed from this repository because it does not contain any kie-camel or another fuse-bxms-integ dependency. It is required to include this quickstart and its feature to the jbpm repository: <feature name="fuse-bxms-spring-jbpm-osgi-example" version="${project.version}"> <feature version="${karaf.version.org.kie}">kie-spring</feature> <bundle>mvn:org.jboss.integration.fuse.quickstarts/spring-jbpm-osgi-example/${project.version}</bundle> </feature> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6339) Upgrade HAL to 2.8.23.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-6339: --------------------------------- Summary: Upgrade HAL to 2.8.23.Final Key: WFLY-6339 URL: https://issues.jboss.org/browse/WFLY-6339 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Priority: Blocker Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6339) Upgrade HAL to 2.8.23.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-6339?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-6339: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/8707) > Upgrade HAL to 2.8.23.Final > --------------------------- > > Key: WFLY-6339 > URL: https://issues.jboss.org/browse/WFLY-6339 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Blocker > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-437) Elytron compilation fails with IBM JDK

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/ELY-437?page=com.atlassian.jira.plugin.sy... ] Tomaz Cerar commented on ELY-437: --------------------------------- created CI job for ibm https://ci.wildfly.org/viewType.html?buildTypeId=WildFlyProject_Elytron_M... > Elytron compilation fails with IBM JDK > -------------------------------------- > > Key: ELY-437 > URL: https://issues.jboss.org/browse/ELY-437 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.CR1 > > > Compilation of wildfly-elytron project with IBM JDK 1.8 fails with: > {code} > wildfly-elytron/src/main/java/org/wildfly/security/x500/X500PrincipalUtil.java:[31,25] cannot find symbol > symbol: class X500Name > location: package sun.security.x509 > {code} > Class X500PrincipalUtil using sun.security.x509.X500Name which comes from internal API and leads to mentioned above issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-437) Elytron compilation fails with IBM JDK

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-437: -------------------------------- Summary: Elytron compilation fails with IBM JDK Key: ELY-437 URL: https://issues.jboss.org/browse/ELY-437 Project: WildFly Elytron Issue Type: Bug Affects Versions: 1.1.0.Beta4 Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Fix For: 1.1.0.CR1 Compilation of wildfly-elytron project with IBM JDK 1.8 fails with: {code} wildfly-elytron/src/main/java/org/wildfly/security/x500/X500PrincipalUtil.java:[31,25] cannot find symbol symbol: class X500Name location: package sun.security.x509 {code} Class X500PrincipalUtil using sun.security.x509.X500Name which comes from internal API and leads to mentioned above issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016