November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5817) Update to 1003px grid system

by Heiko Braun (JIRA)

Heiko Braun created AS7-5817: -------------------------------- Summary: Update to 1003px grid system Key: AS7-5817 URL: https://issues.jboss.org/browse/AS7-5817 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 Modern times... -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-5903) OSGi tests may incorrectly assume that a given service is available

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5903: ----------------------------------- Summary: OSGi tests may incorrectly assume that a given service is available Key: AS7-5903 URL: https://issues.jboss.org/browse/AS7-5903 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Similar to AS7-5828 there may be other tests that could potentially fail because of an invalid assumption that a given service is available. This may especially happen if the test before changes the framework startlevel. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5902) HornetQ does not delete message from queue when the message is rolled back and the DLQ is not present

by Ravi Bhardwaj (JIRA)

Ravi Bhardwaj created AS7-5902: ---------------------------------- Summary: HornetQ does not delete message from queue when the message is rolled back and the DLQ is not present Key: AS7-5902 URL: https://issues.jboss.org/browse/AS7-5902 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.2.Final (EAP) Reporter: Ravi Bhardwaj Assignee: Jeff Mesnil When a message is rolled back and the DLQ binding configured for queue is missing, the server throws the following warning message saying that it is dropping the message, however we can still see the message count and In Delivery count as : WARN [org.hornetq.core.server.impl.QueueImpl] (Thread-3 (HornetQ-server-HornetQServerImpl::serverUUID=c7787105-2983-11e2-94d2-611405d536ca-619601171)) Message Reference[143]:RELIABLE:ServerMessage[messageID=143,priority=4, bodySize=178,expiration=0, durable=true, address=jms.queue.TestQ2,properties=TypedProperties[null]]@1575145817 has exceeded max delivery attempts. No bindings for Dead Letter Address jms.queue.DLQ123 so dropping it -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3682) Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ] Michael Anstis moved GUVNOR-1967 to JBRULES-3682: ------------------------------------------------- Project: Drools (was: Guvnor) Key: JBRULES-3682 (was: GUVNOR-1967) Issue Type: Task (was: Enhancement) Affects Version/s: 5.3.0.Final (was: drools-5.3.0.Final) > Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR. > --------------------------------------------------------------------------------------------- > > Key: JBRULES-3682 > URL: https://issues.jboss.org/browse/JBRULES-3682 > Project: Drools > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Environment: local > Reporter: Amit Telang > Labels: maven > > Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr. > If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time. > Please provide any valuable feedback if someone also faces this issue. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3682) drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3682?page=com.atlassian.jira.plug... ] Michael Anstis updated JBRULES-3682: ------------------------------------ Summary: drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR. (was: Guvnor drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR.) > drools-compiler jar file dependancy with antlr3.3 creating issue in deployment of EAR. > --------------------------------------------------------------------------------------- > > Key: JBRULES-3682 > URL: https://issues.jboss.org/browse/JBRULES-3682 > Project: Drools > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.3.0.Final > Environment: local > Reporter: Amit Telang > Labels: maven > > Hi, after inclusion guvnor 5.x in application, we are unable to deploy our application through Hudson on our managed server. Issue is related to drools-compiler-5.3.0.Final.jar dependancy with antlr3.3 jar file. If I use exclusion tag to exclude this it excludes all the jar which starts with antlr. > If I use package exclude to include this antlr3.3 it do not compile. Unable to resolve this small looking issue for a long time. > Please provide any valuable feedback if someone also faces this issue. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4692) Review SecurityContext associations

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4692: ------------------------------------- Summary: Review SecurityContext associations Key: AS7-4692 URL: https://issues.jboss.org/browse/AS7-4692 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 We should re-review the approach we take for security context association within AS7 containers. Back at the time of AS 3 it fairly reliable to assume a 1:1 mapping of thread and client with the incoming connection being allocated it's own thread, this is no longer automatically the case and different containers can use different threading models e.g. using Executors to handle asynchronous requests. The problem with using a ThreadLocal approach is that every time a container diverges from the 1:1 mapping of thread and client that container needs to work around the issue of an invalid SecurityContext association. One possibility is to pass responsibility for managing the context to the container although this then introduces the question of how it is passed from container to container. This issue needs to consider this further. Also need to review further how the security context can be created at all entry points to the server and how it can be manually switched now that we use SASL on entry for remote calls we do now have the opportunity for equivalent behaviour at the entry point for both web and ejb type calls - in the past we only had this opportunity for web based calls and would only create a security context on entering the interceptors for the EJB calls. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4693) Revisit authenticated user / authorized user split

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4693: ------------------------------------- Summary: Revisit authenticated user / authorized user split Key: AS7-4693 URL: https://issues.jboss.org/browse/AS7-4693 Project: Application Server 7 Issue Type: Task Components: Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 When establishing a connection a remote user can specify the user they want to be authorized as which can be different to the user they authenticate as, e.g. a user with appropriate permissions may want to connect as an administrator or a user given access to someone elses account may want to connect as them. We need to re-visit this including validation that they can connect as the user they are asking to. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4665) Re visit authentication tokens

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4665: ------------------------------------- Summary: Re visit authentication tokens Key: AS7-4665 URL: https://issues.jboss.org/browse/AS7-4665 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.2.Final-redhat1 We had previously considered authentication tokens for the realm secured interfaces, this issue is just to track re-considering them again. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-5047) Allow more control over authentication for server to server communication through remote-outbound-connection

by jaikiran pai (JIRA)

jaikiran pai created AS7-5047: --------------------------------- Summary: Allow more control over authentication for server to server communication through remote-outbound-connection Key: AS7-5047 URL: https://issues.jboss.org/browse/AS7-5047 Project: Application Server 7 Issue Type: Feature Request Components: Security Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: jaikiran pai Assignee: Anil Saldhana Right now for server to server communication via a remote-outbound-connection, we expect a static username to be specified (along with the security realm). User applications which use this remote-outbound-connection, for example an EJB application, do not have much control over the user/pass information, since the username is static. This further acts a drawback since the username that's used to connect to the remote server will be used as the (application) user who invoked the EJB. It would be good to allow more control over the authentication for the remote-outbound-connection. -- 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, 11 months

5
9
0 / 0

[JBoss JIRA] (AS7-5901) Connection Reauthentication and Security Propagation

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5901: ------------------------------------- Summary: Connection Reauthentication and Security Propagation Key: AS7-5901 URL: https://issues.jboss.org/browse/AS7-5901 Project: Application Server 7 Issue Type: Task Components: EJB, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.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

12 years, 11 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 November 2012