Hi Marvin, I know this is a matter of CAS-OpenKM integration, but the think i don't uderstand is that with spring.ldap it works and not with spring.cas ....
Le 03/09/2013 15:45, Marvin S. Addison a écrit : >> DEBUG org.jasig.cas.client.validation.Saml11TicketValidator - >> Constructing validation url: >> https://URLCASSERVER:8443/cas/samlValidate?TARGET=http%3A%2F%2FURLCASCLIENT%3A8080%2FOpenKM%2Flogo%2Flogin%3FTARGET%3Dhttp%253A%252F%252FURLCASCLIENT%253A8080%252FOpenKM%252Flogo%252Flogin >> >> DEBUG org.jasig.cas.client.validation.Saml11TicketValidator - Retrieving >> response from server. >> DEBUG org.jasig.cas.client.validation.Saml11TicketValidator - Server >> response: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope >> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Header/><SOAP-ENV:Body><Response >> >> xmlns="urn:oasis:names:tc:SAML:1.0:protocol" >> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" >> xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol" >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> IssueInstant="2013-09-02T21:36:13.944Z" MajorVersion="1" >> MinorVersion="1" Recipient="http://URLCASCLIENT:8080/OpenKM/logo/login"; >> ResponseID="_14ce5945f0cce6759da22bafb98facd4"><Status><StatusCode >> Value="samlp:Success"></StatusCode></Status><Assertion >> xmlns="urn:oasis:names:tc:SAML:1.0:assertion" >> AssertionID="_5216abc4e65335471bb6a5330a3bf9a3" >> IssueInstant="2013-09-02T21:36:13.944Z" Issuer="localhost" >> MajorVersion="1" MinorVersion="1"><Conditions >> NotBefore="2013-09-02T21:36:13.944Z" >> NotOnOrAfter="2013-09-02T21:36:43.944Z"><AudienceRestrictionCondition><Audience>http://URLCASCLIENT:8080/OpenKM/logo/login</Audience></AudienceRestrictionCondition></Conditions><AttributeStatement><Subject><NameIdentifier>g.lemaire</NameIdentifier><SubjectConfirmation><ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:artifact</ConfirmationMethod></SubjectConfirmation></Subject><Attribute >> >> AttributeName="roleAttributeNames" >> AttributeNamespace="http://www.ja-sig.org/products/cas/";><AttributeValue>DEMOVILLE</AttributeValue></Attribute></AttributeStatement><AuthenticationStatement >> >> AuthenticationInstant="2013-09-02T21:18:02.862Z" >> AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified"><Subject><NameIdentifier>g.lemaire</NameIdentifier><SubjectConfirmation><ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:artifact</ConfirmationMethod></SubjectConfirmation></Subject></AuthenticationStatement></Assertion></Response></SOAP-ENV:Body></SOAP-ENV:Envelope> >> >> DEBUG org.jasig.cas.client.validation.Saml11TicketValidationFilter - >> Successfully authenticated user: g.lemaire >> DEBUG org.jasig.cas.client.validation.Saml11TicketValidationFilter - >> Redirecting after successful ticket validation. > > That much indicates a successful CAS authentication; your SAML > attribute response even contains attributes that presumably are > required for authorization. Everything following is a matter of > CAS-OpenKM integration, and I can't provide any help in that regard. > >> DEBUG org.jasig.cas.client.util.CommonUtils - serviceUrl generated: >> http://URLCASCLIENT:8080/OpenKM/logo/login?TARGET=http%3A%2F%2FURLCASCLIENT%3A8080%2FOpenKM%2Flogo%2Flogin >> >> DEBUG com.openkm.core.UINotification - *** Clean UI notification *** >> DEBUG com.openkm.servlet.frontend.UINotificationServlet - clean() > > Anyone else have any experience with OpenKM? > > Thanks, > M > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
