February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1744) Remove use of java.security.acl APIs

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1744?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1744: ---------------------------- Fix Version/s: 1.8.0.CR3 (was: 1.8.0.CR2) > Remove use of java.security.acl APIs > ------------------------------------ > > Key: ELY-1744 > URL: https://issues.jboss.org/browse/ELY-1744 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.8.0.CR3 > > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within WildFly Elytron we only seem to use it in the JAAS security realm which I don't believe is used although likely is public API. I believe the use was to mirror some PicketBox behaviour. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1751) Release WildFly Elytron 1.8.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1751?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1751. ----------------------------- Resolution: Done > Release WildFly Elytron 1.8.0.CR2 > --------------------------------- > > Key: ELY-1751 > URL: https://issues.jboss.org/browse/ELY-1751 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.8.0.CR2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-584) Create rover group and pair it with istioci project

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-584?page=com.atlassian.jira.plugin.... ] Filip Brychta edited comment on SWSQE-584 at 2/4/19 2:07 PM: ------------------------------------------------------------- Created https://redhat.service-now.com/surl.do?n=PNT0476634 was (Author: fbrychta): Created https://redhat.service-now.com/surl.do?n=PNT0459175 > Create rover group and pair it with istioci project > --------------------------------------------------- > > Key: SWSQE-584 > URL: https://issues.jboss.org/browse/SWSQE-584 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > > There's a change in the authentication process in the new environment. In CI-RHOS we have used only local authentication and most teams only used shared account to login to the environment. In PSI (Upshift) we switched to LDAP authentication, thus you use your Kerberos credentials to log in to the system. What we do during the initial setup is paring of the Rover group name with the particular project and then it's up to Rover group admins to manage people who should be able to access the resources in PSI. That's why we need the Rover group name from you. > When creating a Rover group please give it a different name than your LDAP group. Ambiguity could be a potential problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-584) Create rover group and pair it with istioci project

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-584?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-584: ------------------------------------- Created https://redhat.service-now.com/surl.do?n=PNT0459175 > Create rover group and pair it with istioci project > --------------------------------------------------- > > Key: SWSQE-584 > URL: https://issues.jboss.org/browse/SWSQE-584 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > > There's a change in the authentication process in the new environment. In CI-RHOS we have used only local authentication and most teams only used shared account to login to the environment. In PSI (Upshift) we switched to LDAP authentication, thus you use your Kerberos credentials to log in to the system. What we do during the initial setup is paring of the Rover group name with the particular project and then it's up to Rover group admins to manage people who should be able to access the resources in PSI. That's why we need the Rover group name from you. > When creating a Rover group please give it a different name than your LDAP group. Ambiguity could be a potential problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-158) Unauthorized access exception when closing JMX console and RBAC is set on server

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/REMJMX-158?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-158. ------------------------------------- Resolution: Done > Unauthorized access exception when closing JMX console and RBAC is set on server > -------------------------------------------------------------------------------- > > Key: REMJMX-158 > URL: https://issues.jboss.org/browse/REMJMX-158 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Reporter: Richard Opalka > Assignee: Brad Maxwell > Priority: Major > Fix For: 3.0.1.CR1, 3.1.0.Beta1 > > > javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1204) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1190) > at org.jboss.as.jmx.PluggableMBeanServerImpl.removeNotificationListener(PluggableMBeanServerImpl.java:946) > at org.jboss.as.jmx.BlockingNotificationMBeanServer.removeNotificationListener(BlockingNotificationMBeanServer.java:243) > at org.jboss.as.jmx.AuthorizingMBeanServer.removeNotificationListener(AuthorizingMBeanServer.java:352) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:229) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListeners(ServerProxy.java:239) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:222) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.access$1900(ServerProxy.java:199) > at org.jboss.remotingjmx.protocol.v2.ServerProxy.end(ServerProxy.java:167) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever.handleEnd(ServerCommon.java:216) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:291) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:957) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-159) Release Remoting JMX 3.0.1.Final

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/REMJMX-159?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-159. ------------------------------------- Resolution: Done > Release Remoting JMX 3.0.1.Final > -------------------------------- > > Key: REMJMX-159 > URL: https://issues.jboss.org/browse/REMJMX-159 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 3.0.1.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4310) Upgrade Remoting JMX to 3.0.1.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4310: ---------------------------------------- Summary: Upgrade Remoting JMX to 3.0.1.Final Key: WFCORE-4310 URL: https://issues.jboss.org/browse/WFCORE-4310 Project: WildFly Core Issue Type: Component Upgrade Components: JMX Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Beta4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-159) Release Remoting JMX 3.0.1.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created REMJMX-159: --------------------------------------- Summary: Release Remoting JMX 3.0.1.Final Key: REMJMX-159 URL: https://issues.jboss.org/browse/REMJMX-159 Project: Remoting JMX Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.1.CR1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2974) CLI completion after one or more spaces gives confusing result

by Jean-Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-2974?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2974: ---------------------------------------------- [~vmarek], I am more concerned by introducing regression. I am pretty sure we would manage to fix it, but being an edge case, I would prefer not fix it. > CLI completion after one or more spaces gives confusing result > -------------------------------------------------------------- > > Key: WFCORE-2974 > URL: https://issues.jboss.org/browse/WFCORE-2974 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Beta26 > Reporter: Chao Wang > Assignee: Jean-Francois Denise > Priority: Minor > > CLI completion after one or more spaces gives confusing result. > {noformat} > [standalone@localhost:9990 /] /sub[space]TabKey Here > above completion returns result: > [standalone@localhost:9990 /] /sub ystem= > It seems the space before TabKey is recognized as character 's'. > Go on for a second TabKey, it will not list any subsystem candidates. > {noformat} > I think the first completion is not necessary as the {{sub}} with a following space is not a valid path. It'd better stop there rather than return completion result {{/sub ystem=}}. But this is a minor case. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-158) Unauthorized access exception when closing JMX console and RBAC is set on server

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/REMJMX-158?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated REMJMX-158: ------------------------------------ Fix Version/s: 3.0.1.CR1 > Unauthorized access exception when closing JMX console and RBAC is set on server > -------------------------------------------------------------------------------- > > Key: REMJMX-158 > URL: https://issues.jboss.org/browse/REMJMX-158 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Reporter: Richard Opalka > Assignee: Brad Maxwell > Priority: Major > Fix For: 3.0.1.CR1, 3.1.0.Beta1 > > > javax.management.JMRuntimeException: WFLYJMX0037: Unauthorized access > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1204) > at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1190) > at org.jboss.as.jmx.PluggableMBeanServerImpl.removeNotificationListener(PluggableMBeanServerImpl.java:946) > at org.jboss.as.jmx.BlockingNotificationMBeanServer.removeNotificationListener(BlockingNotificationMBeanServer.java:243) > at org.jboss.as.jmx.AuthorizingMBeanServer.removeNotificationListener(AuthorizingMBeanServer.java:352) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:229) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListeners(ServerProxy.java:239) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.removeNotificationListener(ServerProxy.java:222) > at org.jboss.remotingjmx.protocol.v2.ServerProxy$RemoteNotificationManager.access$1900(ServerProxy.java:199) > at org.jboss.remotingjmx.protocol.v2.ServerProxy.end(ServerProxy.java:167) > at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever.handleEnd(ServerCommon.java:216) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:291) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:957) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019