[JBoss JIRA] Updated: (JBAS-2854) Fire local transaction events from the jms resource adapter
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2854?page=all ]
Dimitris Andreadis updated JBAS-2854:
-------------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.CR1)
Moving issue to a next release
> Fire local transaction events from the jms resource adapter
> -----------------------------------------------------------
>
> Key: JBAS-2854
> URL: http://jira.jboss.com/jira/browse/JBAS-2854
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.4RC1
> Reporter: Adrian Brock
> Assigned To: Weston Price
> Fix For: JBossAS-4.2.1.CR1
>
>
> We need to fire local transaction events from the jms resource adapter.
> This is not a trivial change since there is currently no easy way for the JmsSession class
> to work out when the transaction started and whether it is a local transaction.
> There is no explicit start of transaction in JMS.
> It probably needs a modfication to getSession() as this is the most obvious point
> where work is first done in a new transaction after the commit/rollback on the session.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Updated: (JBAS-3325) Remove old code
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3325?page=all ]
Dimitris Andreadis updated JBAS-3325:
-------------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.CR1)
Moving issue to a next release
> Remove old code
> ---------------
>
> Key: JBAS-3325
> URL: http://jira.jboss.com/jira/browse/JBAS-3325
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Other
> Affects Versions: JBossAS-4.0.4.GA
> Environment: JBoss 4.0.3.SP1
> $ java -version
> java version "1.4.2_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
> $ java -version
> java version "1.5.0_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)
> Reporter: Robert Schroeder
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.1.CR1
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall mentions the parameter "java.rmi.server.hostname" to set if the external host name differs from the local host (e.g. server machine is behind a firewall)
> But org.jboss.web.WebService doesn'r recognize this parameter:
> String hostname = server.getBindAddress(); // this always returns something, at least "0.0.0.0"!
> // If not user specified hostname given, then try to determine what it should be
> if (hostname == null) //this branch is never executed!
> {
> // First look for the rmi server name
> try
> {
> hostname = System.getProperty("java.rmi.server.hostname"); // this parameter is not recognized as this branch is never executed
> }
> catch (SecurityException e)
> {
> // ignore, but don't be silent
> ThrowableHandler.addWarning(e);
> }
> // else use the localhost name
> if (hostname == null)
> {
> try
> {
> hostname = InetAddress.getLocalHost().getHostName();
> }
> catch (IOException e)
> {
> log.error("Failed to get localhost name; ignoring", e);
> }
> }
> if (hostname != null)
> {
> setHost(hostname);
> }
> }
> // Host must be set to continue (either by user or detection)
> String address = getHost();
> if (address == null)
> throw new MissingAttributeException("Host");
> // Set the rmi codebase if it is not already set
> String codebase = System.getProperty("java.rmi.server.codebase");
> if (codebase == null)
> {
> address = ServerConfigUtil.fixRemoteAddress(address);
> codebase = "http://" + address + ":" + getPort() + "/";
> System.setProperty("java.rmi.server.codebase", codebase);
> }
> log.info("Using RMI server codebase: " + codebase);
> So the resulting problem is that codebase contains an address which is not reachable from the other side of firewall because "java.rmi.server.hostname" is not recognized (same for "-Djava.rmi.server.useLocalHostname=false" )
> Example:
> JBoss started with parameter set "-Djava.rmi.server.hostname=as2.subdomain1.subdomain2.test.com"
> but (thanks to rmi logging) the proxy objects on client side have codebase set to "http://as2:<port>" and not to "http://as2.subdomain1.subdomain2.test.com:<port>" as expected.
> JBoss 4 runs on a linux machine
> hostname --> "as2"
> hostname -f --> "as2.subdomain1.subdomain2.test.com"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Updated: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ]
Dimitris Andreadis updated JBAS-1824:
-------------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.CR1)
Moving issue to a next release
> JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass
> ----------------------------------------------------------------------------------------
>
> Key: JBAS-1824
> URL: http://jira.jboss.com/jira/browse/JBAS-1824
> Project: JBoss Application Server
> Issue Type: Feature Request
> Components: Security
> Affects Versions: JBossAS-4.0.2 Final
> Environment: -
> Reporter: Roland R?z
> Assigned To: Anil Saldhana
> Fix For: JBossAS-4.2.1.CR1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is.
> Therefore the accessing user must login.
> So my web.xml contains the following snippet:
> ...
> <security-constraint>
> <web-resource-collection>
> <web-resource-name>Protected Helloworld example</web-resource-name>
> <description/>
> <url-pattern>/servlet/HelloWorldExample</url-pattern>
> <http-method>POST</http-method>
> <http-method>GET</http-method>
> </web-resource-collection>
> <auth-constraint>
> <role-name>*</role-name>
> </auth-constraint>
> </security-constraint>
> <login-config>
> <auth-method>BASIC</auth-method>
> <realm-name>public</realm-name>
> </login-config>
> ...
> The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss.
> To run it in Jboss I have to add the following element:
> <security-role>
> <role-name>aRole</role-name>
> </security-role>
> The JACC spec (section 3.1.3.1, paragraph 3)states :
> " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application."
> JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml.
> But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml.
> It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml.
> Or is this a JACC spec issue?
> Regards,
> Andrea
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months