<div dir="ltr">Not sure if anyone who is using the MCB is also using Shibboleth with Webex.<div><br></div><div>Webex has an SSO configuration console and one of the options is AuthnContextClassRef. </div><div><br></div><div>I have this configured to be:</div><div>urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport</div><div><div><br></div><div>My MCB is configured to allow DUO to satisfy this context. </div><div><br></div>
<p class=""><context name="urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport" method="passwordProtectedTransport"><br> <allowedContexts><br> <context name="<a href="http://brown.edu/duo">http://brown.edu/duo</a>" /><br> </allowedContexts><br></context></p><div><br></div><div> When I authenticate, my IDP generates an assertion with "<a href="http://brown.edu/duo">http://brown.edu/duo</a>" as my authentication context.</div><div><br></div><div>Webex rejects this because it does not match the configured value.</div><div><br></div><div>When I looked closer at the authentication request, I noticed that Webex does not actually include the configured AuthnContextClassRef in its authentication request in a RequestedAuthnContext element. In fact, it does not include a RequestedAuthnContext element at all.</div><div><br></div><div>I am trying to figure out if this is a configuration issue on my part or an implementation issue with Webex.</div><div><br></div><div>Thanks.</div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Christopher Keith '12 ScM<br>Associate Director<div>Integration & Identity Services</div><div>Computing and Information Services<br>Brown University<br>(401) 863-1153</div></div></div>
</div></div>