March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2245) credential-reference capability-reference constraint

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2245?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2245: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > credential-reference capability-reference constraint > ---------------------------------------------------- > > Key: WFCORE-2245 > URL: https://issues.jboss.org/browse/WFCORE-2245 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta8 > > > There attribute credential-reference is defined in many subsystems as below. Looks like the capability-reference constraint should be set in the "store" field of the value-type, therefore I request a review on this capability-constraint placement. > {code} > "credential-reference" => { > "type" => OBJECT, > "description" => "Credential (from Credential Store) to authenticate on data source", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.credential-store", > "access-constraints" => {"sensitive" => { > "credential" => {"type" => "core"}, > "data-source-security" => {"type" => "datasources"} > }}, > "value-type" => { > "store" => { > "type" => STRING, > "description" => "The name of the credential store holding the alias to credential", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "alias" => { > "type" => STRING, > "description" => "The alias which denotes stored secret or credential in the store", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "type" => { > "type" => STRING, > "description" => "The type of credential this reference is denoting", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "clear-text" => { > "type" => STRING, > "description" => "Secret specified using clear text (check credential store way of supplying credential/secrets to services)", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > } > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2206) Upgrade to WildFly Elytron 1.1.0.Beta20

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2206?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2206: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > Upgrade to WildFly Elytron 1.1.0.Beta20 > --------------------------------------- > > Key: WFCORE-2206 > URL: https://issues.jboss.org/browse/WFCORE-2206 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2350) In legacy security realms grant RemoteEJBPermission and RemoteTransactionPermission by default.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2350?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2350: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > In legacy security realms grant RemoteEJBPermission and RemoteTransactionPermission by default. > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2350 > URL: https://issues.jboss.org/browse/WFCORE-2350 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta8 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2349) Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2349?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2349: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > Add RemoteManagementPermission and RemoteJMXPermission checks for remote clients. > --------------------------------------------------------------------------------- > > Key: WFCORE-2349 > URL: https://issues.jboss.org/browse/WFCORE-2349 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta8 > > > Other services such as EJB and transactions have a Remote*Permission to verify the remote client has the required permission to use that service - this should be repeated for the management related services to control what a remote client can and can not connect to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2317) Nested attributes are not validated

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2317?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2317: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > Nested attributes are not validated > ----------------------------------- > > Key: WFCORE-2317 > URL: https://issues.jboss.org/browse/WFCORE-2317 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha25 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 3.0.0.Beta8 > > > Attributes of type Object do not have their inner attributes validated for e.g. "requires" and "alternatives". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2352) Migrate the WildFly Elytron subsystem to WildFly Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2352?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2352: ------------------------------------- Fix Version/s: 3.0.0.Beta8 (was: 3.0.0.Beta7) > Migrate the WildFly Elytron subsystem to WildFly Core > ----------------------------------------------------- > > Key: WFCORE-2352 > URL: https://issues.jboss.org/browse/WFCORE-2352 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Beta8 > > > This task is to move the subsystem to WildFly Core. This task is not to add the subsystem to any additional feature packs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8237) Upgrade to xalan 2.7.1.jbossorg-4 and include fix for cve-2014-0107

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8237?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-8237. ------------------------------ > Upgrade to xalan 2.7.1.jbossorg-4 and include fix for cve-2014-0107 > ------------------------------------------------------------------- > > Key: WFLY-8237 > URL: https://issues.jboss.org/browse/WFLY-8237 > Project: WildFly > Issue Type: Task > Components: XML Frameworks > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > > EAP is still using 2.7.1 with our patches on top of it. > It would be wise to upgrade to 2.7.2 and add any missing patches we did to 2.7.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2350) In legacy security realms grant RemoteEJBPermission and RemoteTransactionPermission by default.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2350?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2350: ------------------------------------------ [~dlofthouse] This wasn't listed in your comment for https://github.com/wildfly/wildfly-core/pull/2222 but I think it should be resolved based on that PR. > In legacy security realms grant RemoteEJBPermission and RemoteTransactionPermission by default. > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2350 > URL: https://issues.jboss.org/browse/WFCORE-2350 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Beta7 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1507) Expose features currently provided by ModelController via capabilities usable by extensions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1507?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1507: ------------------------------------- Summary: Expose features currently provided by ModelController via capabilities usable by extensions (was: Expose the ModelController via a capability) > Expose features currently provided by ModelController via capabilities usable by extensions > ------------------------------------------------------------------------------------------- > > Key: WFCORE-1507 > URL: https://issues.jboss.org/browse/WFCORE-1507 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > A server installs ServerService while an HC installs DomainModelControllerService, under different service names but both of which implement Service<ModelController>. To make it easier for subsystems that want ModelController access to work on both a server and an HC, we should create a capability with service type ModelController and have both processes use it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7539) WebSocketTestCase fails with security manager - disable test

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7539?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7539: ----------------------------------- Fix Version/s: 10.2.0.Final > WebSocketTestCase fails with security manager - disable test > ------------------------------------------------------------ > > Key: WFLY-7539 > URL: https://issues.jboss.org/browse/WFLY-7539 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 10.2.0.Final, 11.0.0.Alpha1 > > > With the core 3.0.0.Alpha12 upgrade we see failures in the WebSocketTestCase when run with the security manager enabled. > $mvn clean install -pl testsuite/integration/web/ -Dsecurity.manager=true > For now I am adding a > {code} > Assume.assumeTrue(System.getSecurityManager() == null); > {code} > to skip this test when running with a security manager enabled. The failure when the test is run with a security manager is > {code} > testWebSocket(org.jboss.as.test.integration.web.websocket.WebSocketTestCase) Time elapsed: 0.227 sec <<< ERROR! > java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.net.SocketPermission" "localhost:0" "listen,resolve")" in code source "(vfs:/content/websocket.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.websocket.war:main" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkListen(SecurityManager.java:1131) > at org.wildfly.security.manager.WildFlySecurityManager.checkListen(WildFlySecurityManager.java:392) > at sun.nio.ch.SocketChannelImpl.bind(SocketChannelImpl.java:582) > at sun.nio.ch.SocketAdaptor.bind(SocketAdaptor.java:135) > at org.xnio.nio.WorkerThread.openTcpStreamConnection(WorkerThread.java:263) > at org.xnio.XnioIoThread.openStreamConnection(XnioIoThread.java:237) > at org.xnio.XnioWorker.openStreamConnection(XnioWorker.java:342) > at org.xnio.http.HttpUpgrade$HttpUpgradeState.doUpgrade(HttpUpgrade.java:247) > at org.xnio.http.HttpUpgrade$HttpUpgradeState.access$100(HttpUpgrade.java:165) > at org.xnio.http.HttpUpgrade.performUpgrade(HttpUpgrade.java:129) > at io.undertow.websockets.client.WebSocketClient$ConnectionBuilder.connectImpl(WebSocketClient.java:323) > at io.undertow.websockets.client.WebSocketClient$ConnectionBuilder.connect(WebSocketClient.java:211) > at io.undertow.websockets.jsr.ServerWebSocketContainer.connectToServerInternal(ServerWebSocketContainer.java:463) > at io.undertow.websockets.jsr.ServerWebSocketContainer.connectToServerInternal(ServerWebSocketContainer.java:457) > at io.undertow.websockets.jsr.ServerWebSocketContainer.connectToServer(ServerWebSocketContainer.java:211) > at org.jboss.as.test.integration.web.websocket.WebSocketTestCase.testWebSocket(WebSocketTestCase.java:52) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 March 2017