Perl 6 - the future is here, just unevenly distributed

IRC log for #shibboleth, 2017-01-18

| Channels | #shibboleth index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:49 ilbot3 joined ##shibboleth
14:24 mok joined ##shibboleth
14:24 mok hello!
14:24 mok is there someone?
14:44 srg Hi mok
14:44 srg I might not be helpful, but I'm "someone"
14:46 mok thanks...may be you can help me...I hope
14:46 mok I am working on the IdP attribute resolver but I get a strange error
14:46 mok Is this one
14:46 mok Attribute 'mergeResults' is not allowed to appear in element 'DataConnector'
14:48 mok SAXParse does not allow the mergeResults attribute inside the DataConnector tag
14:48 mok this is my DataConnector tag
14:48 mok <DataConnector id="groupsLDAP" xsi:type="LDAPDirectory"
14:48 mok ldapURL="%{idp.attribute.resolver.LDAP.ldapURL}"
14:48 mok baseDN="%{idp.attribute.resolver.LDAP.baseDN}"
14:48 mok principal="%{idp.attribute.resolver.LDAP.bindDN}"
14:48 mok principalCredential="%{idp.attribute.resolver.LDAP.bindDNCredential}"
14:48 mok useStartTLS="%{idp.attribute.resolver.LDAP.useStartTLS:true}"
14:48 mok connectTimeout="%{idp.attribute.resolver.LDAP.connectTimeout}"
14:48 mok responseTimeout="%{idp.attribute.resolver.LDAP.responseTimeout}"
14:48 mok maxResultSize="100"
14:49 mok mergeResults="true" >
14:49 mok the strange is that in the .xsd the attribute mergeResults is allowed!
14:55 pdurbin mok: you might need tor try the shib users mailing list
14:57 mok yes, thanks...anyway
15:03 mok I have just resolved!
15:04 mok I have to use namespaces in the xml
15:04 mok So it has became
15:05 mok <resolver:DataConnector id="groupsLDAP" xsi:type="dc:LDAPDirectory"
15:05 mok ldapURL="%{idp.attribute.resolver.LDAP.ldapURL}"
15:05 mok baseDN="%{idp.attribute.resolver.LDAP.baseDN}"
15:05 mok principal="%{idp.attribute.resolver.LDAP.bindDN}"
15:05 mok principalCredential="%{idp.attribute.resolver.LDAP.bindDNCredential}"
15:05 mok useStartTLS="%{idp.attribute.resolver.LDAP.useStartTLS:true}"
15:05 mok connectTimeout="%{idp.attribute.resolver.LDAP.connectTimeout}"
15:05 mok responseTimeout="%{idp.attribute.resolver.LDAP.responseTimeout}"
15:05 mok maxResultSize="100"
15:05 mok mergeResults="true" >
15:06 pdurbin good job :)
15:18 Es0teric joined ##shibboleth
15:19 misilot left ##shibboleth
15:22 dstanek joined ##shibboleth
15:34 pv2b joined ##shibboleth
15:58 Es0teric joined ##shibboleth
17:14 Es0teric joined ##shibboleth
18:57 Es0teric joined ##shibboleth
20:21 Es0teric joined ##shibboleth
23:29 synaptech :)
23:29 synaptech hey guys - not sure if you can help an issue I'm having with testshib
23:29 synaptech I was using it successfully a few weeks ago but now seem to be having issues
23:30 synaptech I uploaded my metadata successfully: http://pastebin.com/eGBjzkxi
23:31 synaptech then issued an authnrequest from my SP
23:32 synaptech http://pastebin.com/dBzeGh2W
23:32 synaptech which redirects me to the testshib login page
23:34 synaptech but after I authenticate I'm getting an error: Error Message: No peer endpoint available to which to send SAML response
23:36 synaptech I checked to make sure the authnrequest issuer matches the metadata entityID
23:37 synaptech and the AssertionConsumerServiceURL matches between the two
23:37 synaptech so I'm scratching my head about what could be wrong
23:40 synaptech 18:34:15.370 - ERROR [edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:447] - No return endpoint available for relying party http://mw-wf8-sql12.centricsoftware.com/sso

| Channels | #shibboleth index | Today | | Search | Google Search | Plain-Text | summary