2015-12-08 52 views
1

我自學SAML。我正在使用糾察快速入門:https://github.com/jboss-developer/jboss-picketlink-quickstartsSAML - 服務提供商無法處理請求

我在運行在端口9080中的wildfly 9.0.2中部署了picketlink-federation-saml-idp-basic-wildfly.war,並且在wildfly 9.0.2中部署了picketlink-federation-saml-sp-post-basic-wildfly.war運行在8080端口。我還更新了standalone.xml以更新IDP和SP的安全域。

我在示例中所做的唯一更改是更新picketlink-jbas7的依賴性,因爲示例2.8.0.Beta1-SNAPSHOT中的版本無法解析。我正在使用IDP maven的依賴關係是:

<dependency> 
     <groupId>org.picketlink.distribution</groupId> 
     <artifactId>picketlink-jbas7</artifactId> 
     <version>2.7.0.Final</version> 
     <scope>provided</scope> 
</dependency> 

我現在面臨的問題是,當我登錄到IDP和點擊SP鏈接,我得到異常的SP日誌如下:

23:05:55,833 ERROR [org.picketlink.common] (default task-5) Service Provider could not handle the request.: java.lang.NullPointerException 
at org.picketlink.identity.federation.web.handlers.saml2.SAML2IssuerTrustHandler$SPTrustHandler.handleStatusResponseType(SAML2IssuerTrustHandler.java:143) 
at org.picketlink.identity.federation.web.handlers.saml2.SAML2IssuerTrustHandler.handleStatusResponseType(SAML2IssuerTrustHandler.java:70) 
at org.picketlink.identity.federation.web.process.SAMLHandlerChainProcessor.callHandlerChain(SAMLHandlerChainProcessor.java:67) 
at org.picketlink.identity.federation.web.process.ServiceProviderSAMLResponseProcessor.processHandlersChain(ServiceProviderSAMLResponseProcessor.java:106) 
at org.picketlink.identity.federation.web.process.ServiceProviderSAMLResponseProcessor.process(ServiceProviderSAMLResponseProcessor.java:88) 
at org.picketlink.identity.federation.bindings.wildfly.sp.SPFormAuthenticationMechanism.handleSAML2Response(SPFormAuthenticationMechanism.java:516) 
at org.picketlink.identity.federation.bindings.wildfly.sp.SPFormAuthenticationMechanism.handleSAMLResponse(SPFormAuthenticationMechanism.java:306) 
at org.picketlink.identity.federation.bindings.wildfly.sp.SPFormAuthenticationMechanism.authenticate(SPFormAuthenticationMechanism.java:268) 
at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:339) 
at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:356) 
at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:325) 
at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:138) 
at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:113) 
at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:106) 
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) 
at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) 
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) 
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) 
at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) 
at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) 
at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) 
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:72) 
at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) 
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) 
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) 
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) 
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:282) 
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261) 
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80) 
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172) 
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) 
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) 
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) 

請讓我知道我做錯了什麼。

謝謝

回答

2

我面臨着同樣的問題,從picketbox快速入門學習。我正在使用wildfly 10.1.0.Final。

我注意到的第一件事是,爲了得到 「基本」 工作是必要的(https://github.com/jboss-developer/jboss-picketlink-quickstarts):

  • IDP:picketlink-聯合會,SAML-IDP-基本
  • SP(S): - 基本picketlink-聯合會-SAML-SP-後picketlink-聯合會,SAML-SP重定向消息基本

爲了簡單起見,我將所有生成的.war部署在一個容器中。

兩件事情,幫助我找到發生了什麼事情:

  • 啓用跟蹤調試
  • picketlink的版本是2.5.5.SP2在Wildfly 10SAML2LoginModule被在picketlink-wildfly8-2.5.5.SP2.jar中找不到。

特別是我與登錄模塊收到此錯誤的一個問題:

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 

我所做的是改變登錄模塊:org.picketlink.identity.federation.bindings.jboss.auth。 SAML2LoginModule和快速入門開始工作。