> Feature seems available, see > https://github.com/vt-middleware/ldaptive/issues/105#issuecomment-229068263 > > Do we get closer to a working gssapi setup ?
To the developers... can we make sure that the GSSAPI implementation is appropriately standards-compliant, i.e. handles things like GSS_S_CONTINUE_NEEDED correctly? Many seem to believe that Kerberos is the only GSSAPI mechanism out there (and hence a single round-trip is sufficient), but it is not. I know of two other mechanisms (mech_saml_ec, aka Fedushare, and mech_eap, aka Moonshot) that will require multiple round-trips. Just keeping this on your radar. Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: [email protected] skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/8D31CA31-6A9F-4F32-9DA4-4E5C15760C65%40jisc.ac.uk. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
