February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3346) Security audit logging problem

by Jan Lanik (JIRA)

Jan Lanik created AS7-3346: ------------------------------ Summary: Security audit logging problem Key: AS7-3346 URL: https://issues.jboss.org/browse/AS7-3346 Project: Application Server 7 Issue Type: Bug Components: Security Affects Versions: 7.1.0.CR1b Reporter: Jan Lanik Assignee: Anil Saldhana I used the configuration setup + quick testing as documented here https://community.jboss.org/wiki/JBossAS7SecurityAuditing The audit.log file was created but no events was recorded in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

8
27
0 / 0

[JBoss JIRA] (AS7-2564) Allow genuine cross-origin resource sharing requests for domain management

by Darran Lofthouse (Created) (JIRA)

Allow genuine cross-origin resource sharing requests for domain management -------------------------------------------------------------------------- Key: AS7-2564 URL: https://issues.jboss.org/browse/AS7-2564 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Minor Fix For: 7.2.0.Alpha1 There may be future scenarios where cross-origin requests could be supported such as custom web/admin applications deployed to different to a different server. This issue is to implement both configuration for accepted requests and support for the OPTIONS method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (AS7-2812) Add message in CLI to indicate which authentication method was used.

by Darran Lofthouse (Created) (JIRA)

Add message in CLI to indicate which authentication method was used. -------------------------------------------------------------------- Key: AS7-2812 URL: https://issues.jboss.org/browse/AS7-2812 Project: Application Server 7 Issue Type: Task Components: CLI, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.CR1 I need to review if this is feasible but there are a number of reports coming in where end users believe their server is not secured because our local / silent mechanism is working so quietly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] (AS7-3112) Better integration of service based ServerAuthenticationProviders

by Darran Lofthouse (Created) (JIRA)

Better integration of service based ServerAuthenticationProviders ----------------------------------------------------------------- Key: AS7-3112 URL: https://issues.jboss.org/browse/AS7-3112 Project: Application Server 7 Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final The security configuration of Remoting within AS7 is based on supplying three things: - - The ServerAuthenticationProvider to obtain mechanism specific CallbackHanlders - The OptionMap to control the security mechanisms made available / mandated. - Possibly an initialised SSLContext for XnioSsl if SSL is being enabled. For domain management the capabilities of the backing realm are used to define the security offered i.e. if we have no SSL configuration we can not enable SSL, if the backing store can not return the plain text passwords we can not enable DIGEST. This has been achieved so far by using an intermediary service to define the configuration based on capabilities alone. This task it to take it one step further and allow this intermediary to be defined within the Remoting subsystem and maybe an equivalent for pure domain management to act as both a intermediary to define configuration based on the realm and also to allow additional configuration overrides. i.e. we need to support the additional SASL options available and SSL options available - this will somehow need to be merged / validated with the realm capabilities e.g. if a Realm is incompatible with Digest a user can not force the use of Digest. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (AS7-3405) Authorization Checks for Services over Remoting

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3405: ------------------------------------- Summary: Authorization Checks for Services over Remoting Key: AS7-3405 URL: https://issues.jboss.org/browse/AS7-3405 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final As all services are now moving to be exposed over Remoting connectors they can all be secured using the same realm. This task is to ensure each at the very least has a basis for an authorization check that can be extended for more complex service specific requirements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
6
0 / 0

[JBoss JIRA] (AS7-3977) Serve gzip encoded console resources

by Heiko Braun (JIRA)

Heiko Braun created AS7-3977: -------------------------------- Summary: Serve gzip encoded console resources Key: AS7-3977 URL: https://issues.jboss.org/browse/AS7-3977 Project: Application Server 7 Issue Type: Feature Request Components: Console, Domain Management Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.2.Final To decrease network latency when loading the console form a remote host. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8198) DomainController discovery system

by Brian Stansberry (JIRA)

DomainController discovery system --------------------------------- Key: JBAS-8198 URL: https://jira.jboss.org/browse/JBAS-8198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Mechanism(s) by which a ServerManager finds a DomainController so it can begin the process of integrating into the domain. Task includes the host.xml schema elements to configure this, the domain object model classes behind those elements, and the actual implementation of discovery from both the ServerManager and DomainController sides. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
14
0 / 0

[JBoss JIRA] Created: (JBAS-8139) Ability to rollback AS version updates

by Brian Stansberry (JIRA)

Ability to rollback AS version updates -------------------------------------- Key: JBAS-8139 URL: https://jira.jboss.org/browse/JBAS-8139 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> A fixpack installer that handles version rollbacks would be fantastic. >> Of course it needs to remain flexible to work with JBoss installs that >> have been manually modified. Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (AS7-3974) Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported

by Bela Ban (JIRA)

Bela Ban created AS7-3974: ----------------------------- Summary: Loopback addresses in the range 127.0.0.2 - 127.255.255.255 should be supported Key: AS7-3974 URL: https://issues.jboss.org/browse/AS7-3974 Project: Application Server 7 Issue Type: Feature Request Environment: Linux Fedora 13 Reporter: Bela Ban When starting JBoss like this: "standalone.sh -b 127.0.0.2 -c standalone-ha.xml", the startup fails because 127.0.0.2 cannot be resolved. However, a loopback address should be recognized even if it doesn't resolve to an interface. The code below works for example: {code} InetAddress addr=InetAddress.getByName("127.0.0.5"); boolean is_loopback=addr.isLoopback(); // should be true {code} Loopback addresses are very useful for local testing, ie. starting of multiple JBoss instances on the same box. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8842) Security checks when recursively reading resources

by Emanuel Muckenhuber (JIRA)

Security checks when recursively reading resources -------------------------------------------------- Key: JBAS-8842 URL: https://issues.jboss.org/browse/JBAS-8842 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Alpha1 Reporter: Emanuel Muckenhuber Assignee: Darran Lofthouse Currently the "read-resource" operation (GlobalOperationHandlers.ReadResourceHandler) just clones the subModel when recursively reading resources. We need to make sure that to also check the permissions for the children a node contains. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2012