Bug 778195 (SOA-700)

This is due to two issues

1) src/org/jboss/soa/esb/samples/quickstarts/opensso/Login.xml  should be removed from the source.  Done in SVN

2) For this release  the following  lines did not make it into  $jbossas/server/default/deploy/jbossesb.sar/jbossesb-properties.xml


 <properties name="security">
        <property name="org.jboss.soa.esb.services.security.implementationClass" value="org.jboss.internal.soa.esb.services.security.JaasSecurityService"/>
        <property name="org.jboss.soa.esb.services.security.callbackHandler" value="org.jboss.internal.soa.esb.services.security.UserPassCallbackHandler"/>
        <property name="org.jboss.soa.esb.services.security.configUrl" value="/jaas.login"/>
 </properties> 

Check for inclusion in the next cp.

Workaround Description: Added: remove the extra files and update the jboss-properties.xml as per the comment
Workaround: Added: [Workaround Exists]

keeping open until changes make it into the platform branch

Sorry, for the 2nd update, which is on the 'jbossesb-properties.xml', it should be "

 <properties name="security">
        <property name="org.jboss.soa.esb.services.security.implementationClass" value="org.jboss.internal.soa.esb.services.security.JaasSecurityService"/>
        <property name="org.jboss.soa.esb.services.security.callbackHandler" value="org.jboss.internal.soa.esb.services.security.UserPassCallbackHandler"/>
 </properties>
"

Take out the ' <property name="org.jboss.soa.esb.services.security.configUrl" value="/jaas.login"/> '. 

But as Dan pointed out, it should be fixed in the next build for SOA-P.

It probably needs yet another modification. If I use this I am getting when I am trying to use secured QS
Caused by: javax.security.auth.login.LoginException: Missing users.properties file.
        at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:148)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
        at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
        at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
        at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
        at org.jboss.internal.soa.esb.services.security.JaasSecurityService.authenticate(JaasSecurityService.java:133)

I guess it is necessary to configure it in that way to use soa-users and soa-roles property files.

This is because the webservice_producer_secured example is using the 'CertLogin' module, which should be included in the 'jaas.login' file. but it hasn't been included in the IR2, but I think Daniel is working on this. 

But this is not related to the opensso. ;-).

quickstart works fine if it is the first one started, it fails to deploy if other quickstarts have been run first.

Well, and what about running OpenSSO QS twice in a row?

Well, it seems that opensso.war can't be deployed on the fly, which means you need to deploy the opensso.war first, and then start the server. In this case, it can be deployed successfully.

Besides, I will follow-up the web service clash problem through email.

On this release, we will deploy opensso.war into Tomcat, and for opensso and JBossAS deployment issue, it will be tracked under this jira SOA-731.

Link: Added: This issue related SOA-755

Overcome by events - the QS runs in IR5 - https://jira.jboss.org/jira/browse/SOA-756