<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Webex SSO with OpenID Connect in Webex for Developers</title>
    <link>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4862507#M2258</link>
    <description>&lt;P&gt;OK Janos, I will do so.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jun 2023 13:43:04 GMT</pubDate>
    <dc:creator>Lajos Demeter</dc:creator>
    <dc:date>2023-06-26T13:43:04Z</dc:date>
    <item>
      <title>Webex SSO with OpenID Connect</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4861591#M2250</link>
      <description>&lt;P&gt;I am doing some testing with the Webex SSO using OpenID Connect (OIDC), first for login only, in the "openid email" scope, and found some items which are not fully documented.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My questions the OIDC based SSO behavior of Webex:&lt;/STRONG&gt;&lt;BR /&gt;- could you please confirm that the "JWKS endpoint" is really not used, and if yes, make this mandatory field optional?&lt;BR /&gt;- could you please confirm that the "User info endpoint" is really not used, and make this mandatory field optional?&lt;BR /&gt;- could you please confirm that the returned "access_token" within the OIDC token is not used, so may be empty?&lt;BR /&gt;- could you please confirm that the only the payload part of the returned "id_token" within the OIDC token is used, the other parts can be arbitrary values?&lt;/P&gt;&lt;P&gt;Or am I on a completely wrong path?&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;Background&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;In configuring the OIDC IdP details in Control Hub under "Manually add endpoint information", the CH requests mandatory URLs to the "JWKS endpoint" and "User info endpoint".&lt;/P&gt;&lt;P&gt;According to the IDC standard &lt;A href="https://openid.net/specs/openid-connect-discovery-1_0.html at point 3" target="_self"&gt;HERE&lt;/A&gt;, the JWKS endpoint is REQUIRED and returns key(s) to validate the id_token signature with. The User info endpoint is optional, and serves requests to user details.&lt;/P&gt;&lt;P&gt;In my understanding, the IDP should POST something similar to the Webex idbroker:&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;{&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;"token_type": "Bearer",&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;"expires_in": 3600,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;"access_token": "...",&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;"scope": "email openid",&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;"id_token": "..."&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;}&lt;/FONT&gt;&lt;BR /&gt;and in my understanding the Webex side MUST verify the signature of the id_token using the key(s) downloaded from the "JWKS endpoint", and MAY ask for user details from the "User info endpoint".&lt;/P&gt;&lt;P&gt;However, at least in my tests, it looks like Webex does NOT verify the signature of the id_token, (does not even turn to the "JWKS endpoint" to get the verification key), and ignores the mandatory "iss" (issuer) param in the "id_token" JWT header. It does not turn to the "User info endpoint" either.&lt;BR /&gt;In spite of all these symptoms, the authentication is successful.&amp;nbsp; I found no docs about the OIDC behavior of Webex, while the SAML behavior is quite well documented.&lt;/P&gt;&lt;P&gt;Thanks in advance for your clarification.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Jun 2023 11:21:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4861591#M2250</guid>
      <dc:creator>Lajos Demeter</dc:creator>
      <dc:date>2023-06-24T11:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Webex SSO with OpenID Connect</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4862257#M2254</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1290320"&gt;@Lajos Demeter&lt;/a&gt;&amp;nbsp;would you mind opening a ticket for this please - &lt;A href="mailto:devsupport@webex.com" target="_blank"&gt;devsupport@webex.com&lt;/A&gt;&amp;nbsp;? Please also include the payloads of your testings that you mentioned above, so that we can cross-verify them internally. Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2023 09:55:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4862257#M2254</guid>
      <dc:creator>Janos Benyovszki</dc:creator>
      <dc:date>2023-06-26T09:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Webex SSO with OpenID Connect</title>
      <link>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4862507#M2258</link>
      <description>&lt;P&gt;OK Janos, I will do so.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2023 13:43:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-for-developers/webex-sso-with-openid-connect/m-p/4862507#M2258</guid>
      <dc:creator>Lajos Demeter</dc:creator>
      <dc:date>2023-06-26T13:43:04Z</dc:date>
    </item>
  </channel>
</rss>

