October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBWEB-243) HTTPS / TLS Client certificate authentication does not give client certificate to server side

by Tomas Gustavsson (JIRA)

[ https://issues.jboss.org/browse/JBWEB-243?page=com.atlassian.jira.plugin.... ] Tomas Gustavsson commented on JBWEB-243: ---------------------------------------- Got help from RedHat support (ISV) to debug it, thanks for great support. Can recommend it! > HTTPS / TLS Client certificate authentication does not give client certificate to server side > --------------------------------------------------------------------------------------------- > > Key: JBWEB-243 > URL: https://issues.jboss.org/browse/JBWEB-243 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss AS 7.1.0.GA > Reporter: Tomas Gustavsson > > We use client certificate authentication (TLS) for our webservice (JAX-WS annotated EJB). > In JBoss 5 and 6 the following code worked to fetch the client certificate in the session bean. > MessageContext msgContext = wsContext.getMessageContext(); > HttpServletRequest request = (HttpServletRequest) msgContext.get(MessageContext.SERVLET_REQUEST); > X509Certificate[] certificates = (X509Certificate[]) request.getAttribute("javax.servlet.request.X509Certificate"); > In JBoss AS 7.1.0.GA no certificate is retrieved. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-243) HTTPS / TLS Client certificate authentication does not give client certificate to server side

by Tomas Gustavsson (JIRA)

[ https://issues.jboss.org/browse/JBWEB-243?page=com.atlassian.jira.plugin.... ] Tomas Gustavsson commented on JBWEB-243: ---------------------------------------- Ok, after much struggling I found out it is because of WSDL location rewrite. The wsdl specifies that my webservice in on http://localhost:8080, which is not the SSL port. In JBoss 5 you would simply comment out: <property name="webServiceHost">${jboss.bind.address}</property> In order for the wsdl rewrite to replace the host and port of: <soap:address location="http://localhost:8443/ejbca/ejbcaws/ejbcaws"/> with what was actually used to call the service. In JBoss previous to JBoss 5 this was default (which seems natural to me), in JBoss 5 we had to configure this to workaround. How can we workaround it in JBoss 7? I found in standalone.xml the part with <wsdl-host>. I found the docs at: https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide There I found the <wsdl-host>jbossws.undefined.host</wsdl-host> setting. With that it does work as expected, This issue can be closed. > HTTPS / TLS Client certificate authentication does not give client certificate to server side > --------------------------------------------------------------------------------------------- > > Key: JBWEB-243 > URL: https://issues.jboss.org/browse/JBWEB-243 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss AS 7.1.0.GA > Reporter: Tomas Gustavsson > > We use client certificate authentication (TLS) for our webservice (JAX-WS annotated EJB). > In JBoss 5 and 6 the following code worked to fetch the client certificate in the session bean. > MessageContext msgContext = wsContext.getMessageContext(); > HttpServletRequest request = (HttpServletRequest) msgContext.get(MessageContext.SERVLET_REQUEST); > X509Certificate[] certificates = (X509Certificate[]) request.getAttribute("javax.servlet.request.X509Certificate"); > In JBoss AS 7.1.0.GA no certificate is retrieved. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1521) RELAY2: only some members can become site masters

by Bela Ban (JIRA)

Bela Ban created JGRP-1521: ------------------------------ Summary: RELAY2: only some members can become site masters Key: JGRP-1521 URL: https://issues.jboss.org/browse/JGRP-1521 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.2 Currently, every node in a local cluster (site) can become site master (relaying messages between sites). This requires an internal and external NIC; the former to talk to the local cluster nodes, and the latter to talk to the remote sites. If only a few nodes have multiple NIC, and/or access to the external world, then we should be able to restrict who can become a site master and who cannot. E.g. if we have view {A,B,C,D,E,F}, then perhaps only A and C can become site masters. In this case, if A crashes or leaves, then *C* should become the new site master. Investigate how feasible it is to implement selective site masters. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] (AS7-5667) PlatformLoggingMXBeanSetLoggerLevelHandler does not handle rollback

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5667: ------------------------------------- Summary: PlatformLoggingMXBeanSetLoggerLevelHandler does not handle rollback Key: AS7-5667 URL: https://issues.jboss.org/browse/AS7-5667 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Priority: Minor If this op were called as part of a composite and the composite rolled back, the change made by this handler would not be reversed. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5666) CLONE - CLONE - Transaction isolation level attribute doesn't accept integer values

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-5666?page=com.atlassian.jira.plugin.s... ] Stefano Maestri moved JBPAPP-10080 to AS7-5666: ----------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5666 (was: JBPAPP-10080) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.3.Final (EAP) (was: EAP 6.0.0 ER 6_Beta2) Component/s: JCA (was: JCA) Security: (was: Public) Fix Version/s: 7.2.0.Alpha1 7.1.4.Final (EAP) (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - CLONE - Transaction isolation level attribute doesn't accept integer values > ----------------------------------------------------------------------------------- > > Key: AS7-5666 > URL: https://issues.jboss.org/browse/AS7-5666 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: JBoss-EAP-6-Beta/IronJacamar 1.0.11 > Reporter: Tyronne Wickramarathne > Assignee: Stefano Maestri > Labels: JCA > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > It is not possible to specify an integer value for the Transaction Isolation Level attribute. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5666) Transaction isolation level attribute doesn't accept integer values

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-5666?page=com.atlassian.jira.plugin.s... ] Stefano Maestri updated AS7-5666: --------------------------------- Summary: Transaction isolation level attribute doesn't accept integer values (was: CLONE - CLONE - Transaction isolation level attribute doesn't accept integer values) > Transaction isolation level attribute doesn't accept integer values > ------------------------------------------------------------------- > > Key: AS7-5666 > URL: https://issues.jboss.org/browse/AS7-5666 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: JBoss-EAP-6-Beta/IronJacamar 1.0.11 > Reporter: Tyronne Wickramarathne > Assignee: Stefano Maestri > Labels: JCA > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > It is not possible to specify an integer value for the Transaction Isolation Level attribute. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5666) Transaction isolation level attribute doesn't accept integer values

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-5666?page=com.atlassian.jira.plugin.s... ] Stefano Maestri updated AS7-5666: --------------------------------- > Transaction isolation level attribute doesn't accept integer values > ------------------------------------------------------------------- > > Key: AS7-5666 > URL: https://issues.jboss.org/browse/AS7-5666 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.3.Final (EAP) > Environment: JBoss-EAP-6-Beta/IronJacamar 1.0.11 > Reporter: Tyronne Wickramarathne > Assignee: Stefano Maestri > Labels: JCA > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > It is not possible to specify an integer value for the Transaction Isolation Level attribute. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5511) component upgrade to Hibernate 4.1.7.Final

by Scott Marlow (JIRA)

Scott Marlow created AS7-5511: --------------------------------- Summary: component upgrade to Hibernate 4.1.7.Final Key: AS7-5511 URL: https://issues.jboss.org/browse/AS7-5511 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.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

12 years, 3 months

1
2
0 / 0

[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment

by Philippe Marschall (JIRA)

Philippe Marschall created AS7-5584: --------------------------------------- Summary: Naming context read-only during SAR deployment Key: AS7-5584 URL: https://issues.jboss.org/browse/AS7-5584 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Philippe Marschall During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}} http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi... -- 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, 3 months

3
9
0 / 0

[JBoss JIRA] (AS7-5438) standalone.xml: check if driver name datasource references existing driver in drivers is missing

by Radim Pavlicek (JIRA)

Radim Pavlicek created AS7-5438: ----------------------------------- Summary: standalone.xml: check if driver name datasource references existing driver in drivers is missing Key: AS7-5438 URL: https://issues.jboss.org/browse/AS7-5438 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Environment: GNU/Linux Reporter: Radim Pavlicek Assignee: Jason Greene standalone.xml: <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> <driver name="oracle" module="com.oracle.ojdbc6"> <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class> </driver> </drivers> and in datasource tag: <datasource jta="true" jndi-name="java:jboss/datasources/Glob01DS" pool-name="Glob01DS" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:oracle:thin:....cut</connection-url> <driver>oracle12</driver> wont produce any exception even if I am referencing driver which doesn't exist! -- 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, 3 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2012