1 2 3 Previous Next 61 Replies Latest reply on Feb 28, 2013 12:29 PM by meetoblivion
      • 1. Re: PicketLink 2.0.2.Final is released

        Hi, I just downloaded the latest available JBoss Application Server (Version 7.1.0).  My goal is to activate the PicketLink STS and be able to view its WSDL from a browser.  The cheatsheet[1] says that Picketlink 2.0.1 is already available in the server, and yes, I see the Picketlink jars in the ./modules/org/picketbox/main/ folder. For the time being, that's OK for me instead of Picketlink 2.0.2.  (I can try that later).


        Following the README for JBoss, it tells me to start the server via: /bin/standalone.sh.  OK, I've done that, and I can view the Admin Console at localhost:8080.

        I have some questions:

        1.) When the cheatsheet says that "Picketlink 2.0.1 is already available in the server", does it mean just the JARs (lite distribution) or JARs and WARs (full distribution)?  Do I need the full distribution for the Picketlink STS?

        2.) Will Picketlink STS 2.0.1 activate as soon as I start JBoss (I can't seem to find it in the Admin console), or do I need to install or do something additional for it to start?  The old instructions (https://community.jboss.org/thread/162111) have us deploy something in /server/pl/deploy -- I don't know if I need to do that with AS 7.1.0.

        3.) The cheatsheet says for AS 7.1.0, "You may want to get the latest zip file of the web apps at https://repository.jboss.org/nexus/content/groups/public/org/picketlink/picketlink-fed-webapps-as7-assembly/2.0.2.Final/picketlink-fed-webapps-as7-assembly-2.0.2.Final.zip"  I'm not sure what I need these for--when you say the "latest version" that implies that 7.1.0 has older versions and this download is to update them.  But I can't see anything in 7.1.0 that contains these web apps so do I need them for the Picketlink STS?

        4.) After all is loaded correctly, what is the URL to access the Picketlink STS WSDL?



        [1] https://community.jboss.org/wiki/CheatsheetPicketLinkAndJBossAS

        • 2. Re: PicketLink 2.0.2.Final is released

          The AS 7.x distribution does not contain any web applications.  The jars reside in the modules directory. 

          • 3. Re: PicketLink 2.0.2.Final is released

            I have also been trying to make use of the 2.0.2 distribution with jboss 7.1.0.Final.

            I echo the questions posted by Glen.


            I have been trying to upgrade the jboss module for picketlink but so far without success.

            When I attempt to deploy the idp.war from the 2.0.2 distribution (from item 3 in Glen's posting) I continue to experience a deployment error when I attempt to enable idp.war.


            Please post the module.xml that is required for the 2.0.2 distribution.

            Although my version identifies the resource picketlink-fed-2.0.2.Final.jar and the jar is present I  encounter a ClassNotFoundException for org.picketlink.identity.federation.web.listeners.IDPHttpSessionListener

            • 4. Re: PicketLink 2.0.2.Final is released

              I added a section for AS7.x in https://community.jboss.org/wiki/CheatsheetPicketLinkAndJBossAS


              Gerry, ok.  We will tell you what the problem may be, soon.

              • 5. Re: PicketLink 2.0.2.Final is released

                Hi Gerry,


                     I wrote the following article to help you in updating JBoss AS 7.1.0 to use PicketLink 2.0.2:




                     Please let me know if you have any doubts.



                Pedro Silva

                • 6. Re: PicketLink 2.0.2.Final is released

                  Thanks Pedro.

                  I had done exactly the same procedure as your new article.

                  Just to be sure, I replaced my module.xml with the contents from your article.

                  When I start jboss there are no errors.

                  I completely removed idp.war, restarted jboss and used admin console to add idp.war.

                  No errors.

                  But when I try to enable it, I see:

                  12:46:03,992 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 4403ms - Started 319 of 400 services (78 services are passive or on-demand)

                  12:46:29,424 INFO  [org.jboss.as.repository] (HttpManagementService-threads - 4) JBAS014900: Content added at location C:\s\jboss-7.x\standalone\data\content\ff\90801cb75b94e53a236f03a3ce0ed


                  12:46:44,367 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "idp.war"

                  12:46:44,507 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-11) MSC00001: Failed to start service jboss.deployment.unit."idp.war".POST_MODULE: org.jboss.msc.service.StartException

                  in service jboss.deployment.unit."idp.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "idp.war"

                          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]

                          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]

                          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]

                  Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011093: Could not load component class org.picketlink.identity.federation.web.listeners.IDPHttpSessionListene


                          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:113)

                          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:54)

                          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                          ... 5 more

                  Caused by: java.lang.ClassNotFoundException: org.picketlink.identity.federation.web.listeners.IDPHttpSessionListener from [Module "deployment.idp.war:main" from Service Module Loader]

                          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]

                          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]

                          at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:111)

                          ... 7 more


                  12:46:44,570 INFO  [org.jboss.as.server] (HttpManagementService-threads - 4) JBAS015870: Deploy of deployment "idp.war" was rolled back with failure message {"JBAS014671: Failed services" =>

                  {"jboss.deployment.unit.\"idp.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"idp.war\".POST_MODULE: Failed to process phase POST_MODULE of de

                  ployment \"idp.war\""}}

                  12:46:44,585 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015877: Stopped deployment idp.war in 24ms

                  12:46:44,601 INFO  [org.jboss.as.controller] (HttpManagementService-threads - 4) JBAS014774: Service status report

                  JBAS014777:   Services which failed to start:      service jboss.deployment.unit."idp.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."idp.war".POST_M

                  ODULE: Failed to process phase POST_MODULE of deployment "idp.war"


                  I am using standalone-full.xml in case that matters.

                  Is there possibly another step needed - or another dependency needed  in module.xml ?

                  • 7. Re: PicketLink 2.0.2.Final is released

                    Can you attach a zip file with the modules/org/picketlink/main directory ?



                    Pedro Igor

                    • 8. Re: PicketLink 2.0.2.Final is released

                      An also the the web.xml of your idp.war file ?

                      • 9. Re: PicketLink 2.0.2.Final is released

                        Have you tried unzipping the war zip inside standalone/deployments directory?

                        • 10. Re: PicketLink 2.0.2.Final is released


                          • 11. Re: PicketLink 2.0.2.Final is released

                            attached is the war archive which I deployed using the admin console.

                            In answer to anil, no I didn't try using an exploded war in the deployments folder

                            • 12. Re: PicketLink 2.0.2.Final is released

                              Hi Gerry,


                                  I used the files you attached to configure my environment. Everything works fine, I could deploy and enable the idp.war using de admin console.


                                  I realized that the web.xml in idp.war have no configuration for the org.picketlink.identity.federation.web.listeners.IDPHttpSessionListener. I don't know why you are still getting the ClassNotFoundException if this class is not defined. I did the deploy even with this listener defined.


                                  The only difference I see is the SO. I'm using Linux and it seems that you are using Windows.


                                  I'm also used your standalone-full.xml configuration file.


                                  Try to use a fresh installation of JBoss AS 7.1.0 or remove temporary folders like standalone/data and standalone/tmp. Also, be sure there is no idp.war in the standalone/deployments folder.



                              • 13. Re: PicketLink 2.0.2.Final is released

                                Anil, confusingly, both the "lite" and the "full" Picketlink downloads contain *both* the 2.0.1 and 2.0.2 JARS for the four PicketLink JARs -- do we really need both sets?  Pedro's instructions (https://community.jboss.org/docs/DOC-17625) just have us load in the 2.0.2 jars and ignore the 2.0.1 ones.  If the 2.0.1 ones are unneeded, I think it would be better (less confusing and less potentially buggy) to fix the downloads, this time without the 2.0.1 jars.  Thanks, Glen

                                • 14. Re: PicketLink 2.0.2.Final is released

                                  Anil, I would go a step further, instead of having a "full" and a "lite" download, it's better to have a "jar" and a "war" one, with the JAR download being your present "lite" one and the WAR download (optional for some users) *not* having any of the PicketLink JARs within it.  The WAR download should rely on what is in modules/org/picketlink/main rather than its own PicketLink JARs. 


                                  As I see it, only two steps/downloads are needed: 


                                  1.)  Use the "jar" download to update the JARs in modules/org/picketlink/main -- what you presently call the "lite" download has all this.  I would go a step further and include the updated modules.xml file within the JAR download and a short README telling people to nuke (not append) the old files in this directory and replace it with these. 


                                  2.) For those users who need it, Install the WAR download into standalone/deployments.  Again, this download shouldn't need any PicketLink JARs within it, as JBoss should smoothly run OOTB relying on the updated JARs in modules/org/picketlink/main.

                                  1 2 3 Previous Next