7 Replies Latest reply on Nov 18, 2009 4:29 PM by marcelkolsteren

Seam Integration With JBossIdentity example

tristancollins Nov 4, 2009 10:35 PM

Hi All,

I'm currently trying out the example listed here:

http://www.jboss.org/community/wiki/SeamIntegrationWithJBossIdentity

and from what I can see I'm following all the steps however I'm getting the following exception:

java.lang.RuntimeException: java.lang.IllegalArgumentException: inputstream is null
 at org.jboss.identity.federation.bindings.tomcat.sp.BaseFormAuthenticator.processStart(BaseFormAuthenticator.java:153)
 at org.jboss.identity.federation.bindings.tomcat.sp.BaseFormAuthenticator.start(BaseFormAuthenticator.java:98)
 at org.apache.catalina.core.StandardPipeline.start(StandardPipeline.java:235)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4304)
 at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
 at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
 at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
 at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
 at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
 at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
 at $Proxy38.start(Unknown Source)
 at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
 at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
 at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
 at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
 at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
 at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
 at org.jboss.system.ServiceController.start(ServiceController.java:460)
 at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)
 at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)
 at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
 at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
 at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
 at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
 at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
 at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
 at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
 at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
 at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalArgumentException: inputstream is null
 at org.jboss.identity.federation.web.util.ConfigurationUtil.getHandlers(ConfigurationUtil.java:102)
 at org.jboss.identity.federation.bindings.tomcat.sp.BaseFormAuthenticator.processStart(BaseFormAuthenticator.java:136)
 ... 65 more

As per the instructions:
1. Running a fresh install of JBoss AS 5.1.0.GA

2. I've unpacked the JB Identity jars into server/default/lib being -
jboss-identity-bindings-1.0.0.beta3, identity-bindings-jboss-1.0.0.beta3, identity-fed-1.0.0.beta3 and jbossidm-1.0.0.Beta1

3. deployed saml-sp2.war, saml-sp1.war and saml-idp.war

4. configured the login-config xml

Any ideas?

cheers

1. Re: Seam Integration With JBossIdentity example

marcelkolsteren Nov 8, 2009 4:02 PM (in response to tristancollins)

The example that you tried out was created for the 1.0.0.alpha4 version of JBID. I can imagine that it doesn't work with the 1.0.0.beta3 version. Instead of trying to migrate the example to JBID 1.0.0.beta3, I would advice you to have a look at the following article, which describes a more recent and more elegant way of adding SAMLv2 based SSO to a Seam application:

http://www.jboss.org/community/wiki/JBossSeamsupportforWebBrowserSSOProfile
Actions
2. Re: Seam Integration With JBossIdentity example

tristancollins Nov 8, 2009 4:07 PM (in response to tristancollins)

Great, thanks for that... will give it a go :-)
Actions
3. Re: Seam Integration With JBossIdentity example

marcelkolsteren Nov 8, 2009 7:14 PM (in response to tristancollins)
Triggered by your question, I tried the example Seam application described here:

http://www.jboss.org/community/wiki/JBossIdentityFederationSampleApplications

It suffers from the same problem. Apparently, a new configuration file, named "jbid-handlers.xml" has been introduced for identity providers, but not all sample IDP sample applications have been updated. I will create an issue for that. As a workaround, you can place a file "jbid-handlers.xml" in the WEB-INF directory of the IDP war file, with the following content:

<Handlers xmlns="urn:jboss:identity-federation:handler:config:1.0"> <Handler class="org.jboss.identity.federation.web.handlers.saml2.SAML2LogOutHandler"/> <Handler class="org.jboss.identity.federation.web.handlers.saml2.SAML2AuthenticationHandler"/> </Handlers>
Actions
4. Re: Seam Integration With JBossIdentity example

marcelkolsteren Nov 8, 2009 7:21 PM (in response to tristancollins)

I created a new issue JBID-211 for fixing the sample applications.
Actions
5. Re: Seam Integration With JBossIdentity example

tristancollins Nov 9, 2009 4:55 PM (in response to tristancollins)

Thanks for all your help Marcel.
Actions
6. Re: Seam Integration With JBossIdentity example

machchen Nov 18, 2009 4:35 AM (in response to tristancollins)

I'm trying to work out a sso solution with JbossIdentity. I tried the examples and they work well. However I can't find examples working with the database-I want to store the users and roles in the database(mssql). Could anybody help?

Thanks in advance.
Actions
7. Re: Seam Integration With JBossIdentity example

marcelkolsteren Nov 18, 2009 4:29 PM (in response to tristancollins)

If you use JBoss AS, you could do that as follows. Add a jboss-web.xml file to the WEB-INF directory of your IDP. In the jboss-web.xml, you refer to a security domain, in the form of a JNDI location. In the conf/login-config.xml of the application server, you configure that security domain, using the DatabaseServerLoginModule. When the server starts, it will create the security domain and store a reference to it in JNDI. When the IDP starts, it will lookup the security domain in JNDI.
Actions

Go to original post