<?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: openVulnQuery authorization issues in Services Discussions</title>
    <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4813206#M980</link>
    <description>Hello&lt;BR /&gt;   Changes to OpenVulnQuery were submitted and accepted to main branch; to support the new API changes.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
    <pubDate>Wed, 12 Apr 2023 22:25:27 GMT</pubDate>
    <dc:creator>PR Oxman</dc:creator>
    <dc:date>2023-04-12T22:25:27Z</dc:date>
    <item>
      <title>openVulnQuery authorization issues</title>
      <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4809299#M968</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;
&lt;P&gt;I've followed the instructions and still get authorization errors while using openVulnQuery. So, I've registered an app on apiconsole.cisco.com with app type Service and grant type Client Credentials for &lt;SPAN&gt;Cisco PSIRT openVuln API&lt;/SPAN&gt;. Unfortunately, the provided client id and secret don't seem to work.&lt;/P&gt;
&lt;P&gt;Using the credentials with Postman, I can get the Bearer token but subsequent queries fail with "&lt;SPAN&gt;Not Authorized".&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Using openVulnQuery, I get the following error messages:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: &lt;A href="https://cloudsso.cisco.com/as/token.oauth2?client_id=p3bfx...&amp;amp;client_secret=WRCD.." target="_blank" rel="noopener"&gt;https://cloudsso.cisco.com/as/token.oauth2?client_id=p3bfx...&amp;amp;client_secret=WRCD..&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;What's wrong here? Any help would be appreciated.&lt;/P&gt;
&lt;P&gt;cheers&lt;BR /&gt;rene&lt;/P&gt;</description>
      <pubDate>Thu, 06 Apr 2023 07:17:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4809299#M968</guid>
      <dc:creator>rstraube</dc:creator>
      <dc:date>2023-04-06T07:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: openVulnQuery authorization issues</title>
      <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811532#M973</link>
      <description>&lt;P&gt;Hello Rene,&lt;/P&gt;
&lt;P&gt;Application registered before March 1,2023 will be using URL &lt;A href="https://cloudsso.cisco.com/as/token.oauth2" target="_blank" rel="noopener"&gt;https://cloudsso.cisco.com/as/token.oauth2&lt;/A&gt; (being deprecated). For Application created beginning March 1, 2023 you will use &lt;A href="https://id.cisco.com/oauth2/default/v1/token" target="_blank" rel="noopener"&gt;https://id.cisco.com/oauth2/default/v1/token&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;See &lt;A href="https://raw.githubusercontent.com/api-at-cisco/Images/master/Whats_New_Doc.pdf" target="_blank"&gt;https://raw.githubusercontent.com/api-at-cisco/Images/master/Whats_New_Doc.pdf&lt;/A&gt; for more information.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 02:34:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811532#M973</guid>
      <dc:creator>PR Oxman</dc:creator>
      <dc:date>2023-04-11T02:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: openVulnQuery authorization issues</title>
      <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811626#M978</link>
      <description>&lt;P&gt;Thanks Paul, great information. I did not recognize the new domain for the API endpoint. It helped to get my Postman queries working now.&lt;/P&gt;
&lt;P&gt;openVulnQuery (&lt;A href="https://github.com/CiscoPSIRT/openVulnQuery" target="_blank"&gt;https://github.com/CiscoPSIRT/openVulnQuery&lt;/A&gt;) still does not work with old token generation URL.&lt;/P&gt;
&lt;P&gt;cheers&lt;BR /&gt;rene&lt;/P&gt;</description>
      <pubDate>Tue, 11 Apr 2023 07:36:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811626#M978</guid>
      <dc:creator>rstraube</dc:creator>
      <dc:date>2023-04-11T07:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: openVulnQuery authorization issues</title>
      <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811635#M979</link>
      <description>Thanks Rene,&lt;BR /&gt;                I will check the OpenVulnQuery code.  It will need to be updated.&lt;BR /&gt;&lt;BR /&gt;                Will try to get to that this week.  Or at least prior to May 1st.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 11 Apr 2023 07:45:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4811635#M979</guid>
      <dc:creator>PR Oxman</dc:creator>
      <dc:date>2023-04-11T07:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: openVulnQuery authorization issues</title>
      <link>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4813206#M980</link>
      <description>Hello&lt;BR /&gt;   Changes to OpenVulnQuery were submitted and accepted to main branch; to support the new API changes.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Wed, 12 Apr 2023 22:25:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/openvulnquery-authorization-issues/m-p/4813206#M980</guid>
      <dc:creator>PR Oxman</dc:creator>
      <dc:date>2023-04-12T22:25:27Z</dc:date>
    </item>
  </channel>
</rss>

