April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-42) Jdr utility in combination with IBM JDK (6 or 7 version) generates report, containing empty standalone/domain configuration files

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-42?page=com.atlassian.jira.plugin.sy... ] Jason Greene reassigned WFLY-42: -------------------------------- Assignee: Jesse Jaggars (was: Stuart Douglas) > Jdr utility in combination with IBM JDK (6 or 7 version) generates report, containing empty standalone/domain configuration files > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-42 > URL: https://issues.jboss.org/browse/WFLY-42 > Project: WildFly > Issue Type: Bug > Components: JDR > Environment: IBM JDK > Reporter: Jesse Jaggars > Assignee: Jesse Jaggars > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-440) Add timeout setting for the webservice RemoteDeployer

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-440?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-440: --------------------------------- Assignee: Jim Ma (was: Brian Stansberry) > Add timeout setting for the webservice RemoteDeployer > ----------------------------------------------------- > > Key: WFLY-440 > URL: https://issues.jboss.org/browse/WFLY-440 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 8.0.0.Alpha1 > > > Setting the timeout value to avoid connection timeout failure in the windows test. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1168) MDB is looking up UserTransaction even if it isn't Bean Managed

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1168?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-1168: ------------------------------------ Assignee: Stuart Douglas (was: jaikiran pai) > MDB is looking up UserTransaction even if it isn't Bean Managed > --------------------------------------------------------------- > > Key: WFLY-1168 > URL: https://issues.jboss.org/browse/WFLY-1168 > Project: WildFly > Issue Type: Feature Request > Reporter: Stefano Maestri > Assignee: Stuart Douglas > > Investigating on a use case I've seen that MDB comes to org.jboss.jca.adapters.jdbc.WrapperDataSource looking up for UT. It fails with this exception > javax.naming.NamingException: JBAS014237: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction [Root exception is java.lang.IllegalStateException: JBAS014237: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction] > the problem is exposed running > org.jboss.as.test.integration.ejb.mdb.MDBTestCase -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-442) Review of AccessController and PrivilegedAction use across AS7

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-442?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-442: ------------------------------ Assignee: Darran Lofthouse (was: Scott Marlow) > Review of AccessController and PrivilegedAction use across AS7 > -------------------------------------------------------------- > > Key: WFLY-442 > URL: https://issues.jboss.org/browse/WFLY-442 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > The following needs reviewing across AS7: - > - On demand instantiation of PrivilegedActions where singletons would suffice (Consider frequency of calls, gc may be preferable). > - Use of AccessController even though there is no SecurityManager set. > - Code duplication, in every case I have seen so far the code is the same regardless of if PRIVILEGED or NON_PRIVILEGED > - Utility methods with visibility too high. > - In depth review of the other methods, i.e. if the first thing a public method does is set the class loader based on a parameter passed in it could be used badly - it may even be a justification for that method to NOT use a PrivilegedAction. > - Code that requires to be executed using a PrivilegedAction should also be double checked that it is not doing too much as the identity of the caller. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-447) Connection Reauthentication and Security Propagation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-447?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-447: ------------------------------ Assignee: Darran Lofthouse (was: Thomas Diesler) > Connection Reauthentication and Security Propagation > ---------------------------------------------------- > > Key: WFLY-447 > URL: https://issues.jboss.org/browse/WFLY-447 > Project: WildFly > Issue Type: Task > Components: EJB, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > This task is a top level task to coordinate the addition of support for switching to different security identities on an existing connection over Remoting. > This is to predominantly cover two major scenarios: - > - Clients using a single connection but require different calls to be executed as different users, in this case the client has the information required to start a new authentication as a different user. > - Server to server communication where the first server has already authenticated a remote user - for this scenario the first server needs a way to tell the second server what identity to run the call as. > The following document is building up the requirements and design considerations and decisions: - > https://community.jboss.org/wiki/ConnectionRe-AuthenticationAndSecurityPr... -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-431) Revisit enforcement of required file system permissions.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-431?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-431: ------------------------------ Assignee: Darran Lofthouse (was: Alexey Loubyansky) > Revisit enforcement of required file system permissions. > -------------------------------------------------------- > > Key: WFLY-431 > URL: https://issues.jboss.org/browse/WFLY-431 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-375) Add support to specify ciphers available with Remoting

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-375?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-375: ------------------------------ Assignee: Darran Lofthouse (was: Jeff Mesnil) > Add support to specify ciphers available with Remoting > ------------------------------------------------------ > > Key: WFLY-375 > URL: https://issues.jboss.org/browse/WFLY-375 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-460) Switchable Nonce Handling Strategy for HTTP DigestAuthenticator

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-460?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-460: ------------------------------ Assignee: Darran Lofthouse (was: Scott Marlow) > Switchable Nonce Handling Strategy for HTTP DigestAuthenticator > --------------------------------------------------------------- > > Key: WFLY-460 > URL: https://issues.jboss.org/browse/WFLY-460 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Common_Authentication > Fix For: 8.0.0.Alpha1 > > > Allow the nonce strategy to be switchable: - > 1 - Real 'Number Used Once' - i.e. new nonce for each request. > 2 - Nonce per connection i.e. as long as a connection is kept alive allow re-use of nonce - new nonce on new connection. > 3 - Timed nonce - Generate a nonce with a server secret and timestamp, nonce will be accepted for a validity period. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-475) Re-review CLI server certificate acceptance.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-475?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-475: ------------------------------ Assignee: Darran Lofthouse (was: Brian Stansberry) > Re-review CLI server certificate acceptance. > -------------------------------------------- > > Key: WFLY-475 > URL: https://issues.jboss.org/browse/WFLY-475 > Project: WildFly > Issue Type: Task > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > Can we remove the call loop and manage the user prompt and trust store replacement all within the trust manager? -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-335) Catching custom login module exceptions in remote client

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-335?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-335: ------------------------------ Assignee: Darran Lofthouse (was: Paul Ferraro) > Catching custom login module exceptions in remote client > -------------------------------------------------------- > > Key: WFLY-335 > URL: https://issues.jboss.org/browse/WFLY-335 > Project: WildFly > Issue Type: Feature Request > Components: Remoting, Security, Server > Environment: Win 7 64 Bit > 4 GB RAM > java 1.6 > Reporter: Serkan Yıldırım > Assignee: Darran Lofthouse > Labels: exception, login, login-module, remoting > Fix For: 8.0.0.Alpha1 > > > This feature request is related with the discussion: > https://community.jboss.org/message/732948#732948 > I have custom login modules in JBOSS 7.1.2 Snapshot. They are working with no error, i can authenticate and authorize a user. However, when an exception occurs at the time of login, i.e. wrong password, i throw javax.security.auth.login.LoginException with my custom message. But i couldn't catch the exception in the remote client. Darran said that it's not supported in this version. I think it is a necessary feature because a remote user could be informed why login is failed. -- 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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013