Wildfly 10 compatibility ?

[sandyrhg]

Is there any support for Wildfly 10. Deploying gives me a module error :

Caused by: org.jboss.modules.ModuleLoadError: org.jboss.common-core:main at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1434)

[mh03r932]

I have the same issue. I used the picket link installer 2.7.1 to upgrade wildfly 10 libs to the newest version of picketlink https://docs.jboss.org/picketlink/2/latest/reference/html/PicketLink_Installer.html otherweise there was a different exception.

Now I get this as well

20:45:23,936 WARN [org.jboss.modules] (MSC service thread 1-2) Failed to define class org.picketlink.identity.federation.web.listeners.IDPHttpSessionListener in Module "org.picketlink.federation:main" from local module loader @33e5ccce (finder: local module finder @5a42bbf4 (roots: ...

20:45:23,937 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."picketlink-federation-saml-idp-basic-wildfly.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."picketlink-federation-saml-idp-basic-wildfly.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "picketlink-federation-saml-idp-basic-wildfly.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.modules.ModuleLoadError: org.jboss.common-core:main at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74)

[josehenriqueventura]

The project was merged with the Keycloak, and looks like the Picketlink version was downgraded in Widfly 9/10 to 2.5.5 if I'm not wrong. If any reason you need it in this version, you can find a way to upgrade the Picketlink for the latest version: 2.7.0.Final. Have a look at wildfly-_.Final/modules/system/layers/base/org/picketlink/.._xml files

2016-10-11 19:51 GMT+01:00 mh03r932 notifications@github.com:

I have the same issue 20:45:23,936 WARN [org.jboss.modules](MSC service thread 1-2) Failed to define class org.picketlink.identity.federation.web.listeners.IDPHttpSessionListener in Module "org.picketlink.federation:main" from local module loader @33e5ccce (finder: local module finder @5a42bbf4 (roots: ...

20:45:23,937 ERROR [org.jboss.msc.service.fail](MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit." picketlink-federation-saml-idp-basic-wildfly.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit." picketlink-federation-saml-idp-basic-wildfly.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "picketlink-federation-saml-idp-basic-wildfly.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start( DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run( ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.modules.ModuleLoadError: org.jboss.common-core:main at org.jboss.modules.ModuleLoadException.toError( ModuleLoadException.java:74)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jboss-developer/jboss-picketlink-quickstarts/issues/46#issuecomment-253009694, or mute the thread https://github.com/notifications/unsubscribe-auth/ACP-nOkMqsfkcmnBNUQ1TLvOrV2Sy4dSks5qy9rIgaJpZM4JBBNe .

José Henrique Ventura Software Developer

[cxzero]

I was facing similar problems while using picketlink in Wildfly 10, making PoCs with picketlink quickstarts: https://github.com/jboss-developer/jboss-picketlink-quickstarts/tree/master/picketlink-federation-saml-sp-with-encryption.

In particular I had a problem with login module getting this error:

Class org.picketlink.identity.federation.bindings.wildfly.SAML2LoginModule not found from Module "deployment.picketlink-federation-saml-sp-post-basic-wildfly.war:main" from Service Module Loader

Login failure: javax.security.auth.login.LoginException: unable to find LoginModule class: org.picketlink.identity.federation.bindings.wildfly.SAML2LoginModule

There were two things that helped me find what was going on:

• enable TRACE debug
• version of picketlink is 2.5.5.SP2 in Wildfly 10 and SAML2LoginModule was not found in that package in picketlink-wildfly8-2.5.5.SP2.jar.

What I did was change login module to: org.picketlink.identity.federation.bindings.jboss.auth.SAML2LoginModule and the quickstart started working.

I saw there is a pull request that was merged to update to 2.5.5.SP3 in wildlfy 11: https://github.com/wildfly/wildfly/pull/9087. But ... I saw the latest updated version is 2.5.5.SP8 (Aug/2017) and not 2.7.1.Final (Dec/2015): picketlink federation maven central

Then, in this thread https://issues.jboss.org/browse/PLINK-666 it is said that picket link is deprecated since wildfly 9, so it seems that new developments may use keycloak.

I finish with other question: I am trying to integrate with keyloack in a similar way to picketlink, but kind of all tutorials include having a keycloak standalone server and then configure your applications with keycloak. Do you know a way to integrate keycloak into an existing solution but with the power of customize everything?

Perhaps I am missing some basics, but still I place this question while investigating more.

Regards, Juan

[ctomc]

This is more question that belongs to WildFly quickstart repository, but I can summarize what is the current status around QS & picketlink. Picketlink is deprecated in WildFly as well as in EAP 7.x, it was only tech preview feature when it was added in 6.x times. As replacement there is KeyCloak which is fully supported as a product (RH SSO) and in community.

PL is scheduled to be removed from WildFly at earliest convenience, as such quickstarts containing it ware removed from WildFly quickstarts. EAP Quickstarts still include one QS, but on same level as it was when it was initially added as TP to EAP. That is also the reason why versions of PL ware never upgraded in WildFly beyond patches.

[cxzero]

Thank you for your reply Tomaz!

[alacambra]

What about to use a different IDP (not keycloak) on a wildlfy app? Is the only supported option to install a Keycloak acting as a worker? It does not exist something like a SAML adapter?