[JBoss Portal] - Jboss Portal Clustering (SSO)issue
by rinku05
Hello,
I am using jboss portal 2.6.2 with 4.0.5 AS.
I am facing an issue. I have set the clustered environment with two machines in cluster and Apache webserver2.2 as load balancer.
I have uncommented
in ..\server\all\deploy\jbossweb-tomcat55.sar\server.xml
When I am accessing the portal application, I am directed to one of the server(say server1). Now if I am shutting down the server1, server2 is automatically taking the charge.
As per my understanding if I am uncommenting the above line, there shouldn't be need for user to login again wheh the server1 is down.But the issue is that sometimes user is taken to loging page & has to supply his credentials again(happening for 7 out of 10 times).
Can somebody provide me pointers why this is happening?
Any help will be greatly appreciated.
Regards,
rinku05
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234490#4234490
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234490
14 years, 11 months
[JBossWS] - Re: Implementing WS-Security Usename Token Profile Authentic
by PedroSena
Hi,
I'm trying to implement this solution, but for some reason, the authentication mecanism is not reading correctly my Soap Header.
I saw in log:
2009-06-01 11:09:24,265 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=null
| 2009-06-01 11:09:24,265 DEBUG [org.jboss.ejb3.security.Ejb3AuthenticationInterceptor] Authentication failure
| javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
| at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:213)
|
And I'm sending:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.netsar.com.br/tnw/bus">
| <soapenv:Header>
| <wsse:Security soapenv:mustUnderstand="1"
| xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..."
| xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit...">
| <wsse:UsernameToken wsu:Id="token-1-1236072936329-25515818">
| <wsse:Username>submarino</wsse:Username>
| <wsse:Password
| Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr...">subm4r1n0</wsse:Password>
| </wsse:UsernameToken>
| </wsse:Security>
| </soapenv:Header>
| <soapenv:Body>
| </soapenv:Body>
| </soapenv:Envelope>
I'm testing it from SoapUI, the message was made manually.
I created a new login entry on login-config.xml, its loading properly the users, but its not authenticating.
Would appreciate some help here,
Regards,
PS
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234486#4234486
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234486
14 years, 11 months
[Security & JAAS/JBoss] - Re: Encrypt KeyStore-Password in a Tomcat-Connetctor for 4.2
by yashendrac
Andre,
I confirmed that it is broken in JBoss5.0.1, I am not sure since when it is broken but it was working on JBoss4.2.1. I also confirmed that it is fixed in JBoss5.1.0
I checked the source code for following classes under jbosswe.jar and jbossweb-service.jar
1.org.jboss.net.ssl.JBossImplementation.java
2.org.jboss.net.ssl.JBossSocketFactory.java
3.org.apache.tomcat.util.net.jsse.JSSESocketFactory
JBossSocketFactory overrides following methods from tomcat's
JSSESocketFactory
protected TrustManager[] getTrustManagers(String keystoreType, String algorithm)
| protected KeyManager[] getKeyManagers(String keystoreType, String algorithm,
| String keyAlias)
|
But in tomcat JSSESocketFactory under JBoss5.0.1, method signatures are changed by adding additional String parameter String keystoreProvider.
So methods are changed to following in tomcat JSSESocketFactory
protected TrustManager[] getTrustManagers(String keystoreType,
| String keystoreProvider, String algorithm)
| protected KeyManager[] getKeyManagers(String keystoreType,
| String keystoreProvider,
| String algorithm,
| String keyAlias)
|
So JBossSocketFactory was not overriding these methods anymore and despite providing SSLImplementation="org.jboss.net.ssl.JBossImplementation" these two methods from JSSESocketFactory were invoked in place of JBossSocketFactory.
This is fixed in JBoss5.1.0
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234480#4234480
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234480
14 years, 11 months