February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1197) Port the legacy jmx-console to AS7

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1197?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1197: ----------------------------------- Fix Version/s: (was: 9.0.0.CR1) > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: WFLY-1197 > URL: https://issues.jboss.org/browse/WFLY-1197 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Darran Lofthouse > Labels: JMX, as7, jmx-console, management_security,, management_sso > Attachments: jmx-console.war, jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1014) Enable CORS

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1014?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1014: ----------------------------------- Labels: management_security, management_sso (was: ) > Enable CORS > ----------- > > Key: WFLY-1014 > URL: https://issues.jboss.org/browse/WFLY-1014 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Harald Pehl > Assignee: Darran Lofthouse > Labels: management_security,, management_sso > Fix For: 9.0.0.CR1 > > > We've been prototyping an alternative distribution channel for the console and have setup a demo that leverages the mozilla app store to deliver the AS7 web console to users: > https://marketplace.firefox.com/app/kea/?src=mkt-search > For this to work the AS needs to fully support CORS [1]. The general idea is that you can retrieve the console through a marketplace like the mozilla one (chrome would be another alternative) and connect to any domain controller, wether it runs locally or remotely. > If want to give it shot, point four firefox browser to the marketplace URL, launch the app and connect to our CORS demo instance that runs on EC2: > http://as7-preview.dyndns.org:9990 > user: admin > pass: webstore123! > [1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1197) Port the legacy jmx-console to AS7

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1197?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1197: ----------------------------------- Labels: JMX as7 jmx-console management_security, management_sso (was: JMX as7 jmx-console) > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: WFLY-1197 > URL: https://issues.jboss.org/browse/WFLY-1197 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Darran Lofthouse > Labels: JMX, as7, jmx-console, management_security,, management_sso > Fix For: 9.0.0.CR1 > > Attachments: jmx-console.war, jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1673) Security Realms need a mechanism to allow querying of all known groups and users.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1673?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1673: ----------------------------------- Labels: management_security, management_sso (was: ) > Security Realms need a mechanism to allow querying of all known groups and users. > --------------------------------------------------------------------------------- > > Key: WFLY-1673 > URL: https://issues.jboss.org/browse/WFLY-1673 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security,, management_sso > Fix For: 9.0.0.CR1 > > > As part of the access control development we are adding the capability for users and groups to be associated with roles - for this to be most effective the admin tools need to be able to see the existing groups and users eligible for assignment. > During authentication any queries executed are very targeted towards the currently authenticated user i.e. just searching for that users groups - now we need something to identify all users and groups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1673) Security Realms need a mechanism to allow querying of all known groups and users.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1673?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1673: ----------------------------------- Fix Version/s: (was: 9.0.0.CR1) > Security Realms need a mechanism to allow querying of all known groups and users. > --------------------------------------------------------------------------------- > > Key: WFLY-1673 > URL: https://issues.jboss.org/browse/WFLY-1673 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security,, management_sso > > As part of the access control development we are adding the capability for users and groups to be associated with roles - for this to be most effective the admin tools need to be able to see the existing groups and users eligible for assignment. > During authentication any queries executed are very targeted towards the currently authenticated user i.e. just searching for that users groups - now we need something to identify all users and groups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1652) The security realm PlugIns are currently returning roles, this should be group membership information.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1652?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1652: ----------------------------------- Labels: management_security, (was: ) > The security realm PlugIns are currently returning roles, this should be group membership information. > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-1652 > URL: https://issues.jboss.org/browse/WFLY-1652 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security, > Fix For: 9.0.0.CR1 > > > Without breaking backwards compatibility this should be returning group membership information and not roles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1652) The security realm PlugIns are currently returning roles, this should be group membership information.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1652?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1652: ----------------------------------- Fix Version/s: (was: 9.0.0.CR1) > The security realm PlugIns are currently returning roles, this should be group membership information. > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-1652 > URL: https://issues.jboss.org/browse/WFLY-1652 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security, > > Without breaking backwards compatibility this should be returning group membership information and not roles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1598) Out of the box SSL - or shortly after.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1598?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1598: ----------------------------------- Labels: management_security, management_sso (was: ) > Out of the box SSL - or shortly after. > -------------------------------------- > > Key: WFLY-1598 > URL: https://issues.jboss.org/browse/WFLY-1598 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Labels: management_security,, management_sso > Fix For: 9.0.0.CR1 > > > There are various reasons that we do not support SSL/TLS out of the box e.g. > - If we ship a default keystore then everyone has access to the private key. > - Generating one on first boot we do not have sufficient information to generate it correctly, also the performance overhead. > This issue is to explorer other options to encourage their use and make it easier to configure. > As an example could the admin console detect a non encrypted connection and have an box that encourages the config along with a wizard like workflow to get it set up? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2079) Update security realm <authorization /> to support multiple definitions.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2079?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2079: ----------------------------------- Fix Version/s: (was: 9.0.0.CR1) > Update security realm <authorization /> to support multiple definitions. > ------------------------------------------------------------------------ > > Key: WFLY-2079 > URL: https://issues.jboss.org/browse/WFLY-2079 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > > Complex configuration could result in different methods being used for authentication, as a result we may also need to support multiple sources for loading group membership information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2036) Review of AbstractControllerTestBase

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2036?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2036: ----------------------------------- Fix Version/s: Awaiting Volunteers (was: 9.0.0.CR1) > Review of AbstractControllerTestBase > ------------------------------------ > > Key: WFLY-2036 > URL: https://issues.jboss.org/browse/WFLY-2036 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Alpha4 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Awaiting Volunteers > > > Currently we have the abstract class AbstractControllerTestBase to use as the base for simplified controller testing, however due to visibility problems we now have three versions of this class which have also started to diverge slightly. > Before this goes too far we should try and bring this back down to one. Extensions of this class also have certain amount of common functionality. > Maybe also work converting some of this to a 'org.junit.runner.Runner' to avoid the need for inheritance, additional annotations can then be used to define how to configure the controller being tested. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 February 2014