<?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: How to get Client ID &amp;amp; Client Secret for setting up SCIM with SAS Viya in SAS Viya</title>
    <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849442#M1574</link>
    <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/78975"&gt;@gwootton&lt;/a&gt;&amp;nbsp;covers most everything you need. A couple of follow up notes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The easiest solution here is to create a new client id and generate the access token following the steps in the &lt;A href="https://blogs.sas.com/content/sgf/2021/09/24/authentication-to-sas-viya/" target="_self"&gt;blog post&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;In order to view current clients, you do have to hit the &lt;A href="https://developer.sas.com/apis/rest/CoreServices/#return-collection-of-clients" target="_self"&gt;clients API endpoint&lt;/A&gt;. Note that you need an access token with admin privileges to access the endpoint. That is, include these scopes when registering the client:&amp;nbsp;"scope": ["openid","*","clients.admin"].&lt;/LI&gt;
&lt;LI&gt;I created a &lt;A href="https://github.com/sassoftware/rest-api-use-cases/blob/main/python/authentication/registerClient_generateToken_Python.ipynb" target="_self"&gt;Python Notebook&lt;/A&gt; that registers a new client id and generates an access token. You only need to provide four pieces of info: consul token, SAS server URL, client id and client secret.&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Tue, 13 Dec 2022 16:01:14 GMT</pubDate>
    <dc:creator>joeFurbee</dc:creator>
    <dc:date>2022-12-13T16:01:14Z</dc:date>
    <item>
      <title>How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849282#M1572</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please help me how to get Client ID &amp;amp; Client Secret?&lt;/P&gt;
&lt;P&gt;FYI, SAS Viya was deployed a year back by old Admin. Now Azure Active Directory team telling Security Key/Token is expired.&lt;/P&gt;
&lt;P&gt;So they are asking me to send the new Access token. But I am not sure where the old Client ID &amp;amp; Client secret are present in the environment.&lt;/P&gt;
&lt;P&gt;Can anyone tell me how to get client ID &amp;amp; secret So that I can regenerate the Access token as per below doc?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocumentation.sas.com%2Fdoc%2Fen%2Fcalids%2Fv_001%2Fn1rl3gjjjqmxmfn1hw9ebjjz5778.htm%23p129kkhyady4t2n1cfhrow9a1sjy&amp;amp;data=05%7C01%7Cravindra.poluka%40bp.com%7C20b9026ac091416cba3208dadc9705f9%7Cea80952ea47642d4aaf45457852b0f7e%7C0%7C0%7C638064838433988193%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;amp;sdata=m0kCr6Jgi%2FOMpqw2cZmSfz37GkrizWmjri3JIgENy64%3D&amp;amp;reserved=0" target="_blank"&gt;https://documentation.sas.com/doc/en/calids/v_001/n1rl3gjjjqmxmfn1hw9ebjjz5778.htm#p129kkhyady4t2n1cfhrow9a1sjy&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.sas.com%2Fcontent%2Fsgf%2F2021%2F09%2F24%2Fauthentication-to-sas-viya%2F&amp;amp;data=05%7C01%7Cravindra.poluka%40bp.com%7C20b9026ac091416cba3208dadc9705f9%7Cea80952ea47642d4aaf45457852b0f7e%7C0%7C0%7C638064838433988193%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;amp;sdata=6ARMBJjg8zN9Eoct%2BAh8bDL93S8l1ptxpKQs1lGPhqM%3D&amp;amp;reserved=0" target="_blank"&gt;https://blogs.sas.com/content/sgf/2021/09/24/authentication-to-sas-viya/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here 2nd doc shows I need not to do first 3 steps again now. But I dont have Client credentails -Client ID &amp;amp; Secret?&lt;/P&gt;
&lt;P&gt;Or Are these ID &amp;amp; Secret should be provided by AAD (SCIM Provider)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;RaviSPR&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 23:19:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849282#M1572</guid>
      <dc:creator>RaviSPR</dc:creator>
      <dc:date>2022-12-12T23:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849425#M1573</link>
      <description>When you create a client you provide the client ID and secret (step 5 in the documentation you've linked). You then use that to get a token. You could change the secret if you knew the ID, or you could create a new client and give them a new token. You could also call the SASLogon/oauth/clients endpoint to get a list of all clients.</description>
      <pubDate>Tue, 13 Dec 2022 14:07:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849425#M1573</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2022-12-13T14:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849442#M1574</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/78975"&gt;@gwootton&lt;/a&gt;&amp;nbsp;covers most everything you need. A couple of follow up notes.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The easiest solution here is to create a new client id and generate the access token following the steps in the &lt;A href="https://blogs.sas.com/content/sgf/2021/09/24/authentication-to-sas-viya/" target="_self"&gt;blog post&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;In order to view current clients, you do have to hit the &lt;A href="https://developer.sas.com/apis/rest/CoreServices/#return-collection-of-clients" target="_self"&gt;clients API endpoint&lt;/A&gt;. Note that you need an access token with admin privileges to access the endpoint. That is, include these scopes when registering the client:&amp;nbsp;"scope": ["openid","*","clients.admin"].&lt;/LI&gt;
&lt;LI&gt;I created a &lt;A href="https://github.com/sassoftware/rest-api-use-cases/blob/main/python/authentication/registerClient_generateToken_Python.ipynb" target="_self"&gt;Python Notebook&lt;/A&gt; that registers a new client id and generates an access token. You only need to provide four pieces of info: consul token, SAS server URL, client id and client secret.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 13 Dec 2022 16:01:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849442#M1574</guid>
      <dc:creator>joeFurbee</dc:creator>
      <dc:date>2022-12-13T16:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849542#M1575</link>
      <description>&lt;P&gt;Thanks a lot for the reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Main Issue- Old Secure tokens at Azure AD sites has expired. So I need to provide new Access token to reenable the SCIM for pushing users to SAS Viya.&lt;/P&gt;
&lt;P&gt;I followed 5 steps in the manual Client registration. New issue raised now.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Viya Site-&amp;nbsp;&lt;A href="https://sasviyxxx.xxxxweb.bp.com" target="_blank"&gt;https://sasviyxxx.xxxxweb.xxxxx.com &lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is the site which our Viya users &amp;amp; myself have access &amp;amp; do admin work.&lt;/P&gt;
&lt;P&gt;When I used above site in the 3rd &amp;amp; 5th steps I am getting Bearer Token &amp;amp; Access token. I gave these 2 tokens to&amp;nbsp;Azure AD team for Reauthorizing our SAS Viya through SCIM. But when he click on Test connection in Azure portal with these tokens it is showing invalid credentials.&lt;/P&gt;
&lt;H3 id="n139ou23omw27tn1otyakp4qxzbw" class="xisDoc-title"&gt;Configure SCIM Provisioning in Azure AD&lt;/H3&gt;
&lt;P&gt;&lt;FONT face="helvetica"&gt;&lt;SPAN&gt;In the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Admin Credentials&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;section, complete the following steps:&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;OL class="xisDoc-listSteps" type="a"&gt;
&lt;LI id="p15vgt8lcamf7wn13jd3lqjh4etd" class="xisDoc-step"&gt;&lt;FONT face="helvetica"&gt;In the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Tenant URL&lt;/SPAN&gt;&amp;nbsp;field&lt;/STRONG&gt;, specify the base URL to SAS Viya and append&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE class="xisDoc-directedUserInput"&gt;/identities/scim/v2/&lt;/CODE&gt;.&lt;/FONT&gt;
&lt;DIV id="n1dkzgroo8qsb8n1sr3ge6idcmgi" class="xisDoc-note"&gt;&lt;FONT face="helvetica"&gt;&lt;SPAN class="xisDoc-noteGenText"&gt;Note:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;HTTPS is required. In other words, the ingress controller for your SAS Viya environment is configured for TLS and is using a certificate that is issued by one of the public certificate authorities that are supported by Microsoft Authentication Services.&lt;/FONT&gt;&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI id="p1ws9ibq7tbix7n187rufffufzyz" class="xisDoc-step"&gt;&lt;FONT face="helvetica"&gt;In the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Secret Token&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;field, paste the Bearer token that was created when you followed the process for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A tabindex="0" href="https://documentation.sas.com/doc/en/calcdc/3.5/calids/p17ite7oouumorn1ecsxwh7zxjea.htm#p0ffbdvi9oq1yin1r2ocen1bqj3q" target="_blank"&gt;Manual Client Registration&lt;/A&gt;.&lt;/FONT&gt;&lt;/LI&gt;
&lt;LI id="n0ea38hiigrs40n1d1s9apnnmu7w" class="xisDoc-step"&gt;&lt;FONT face="helvetica"&gt;Click&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Test Connection&lt;/SPAN&gt;.&lt;/FONT&gt;
&lt;P class="xisDoc-paragraph"&gt;&lt;FONT face="helvetica"&gt;If you configured the system correctly, you will receive a successful response.&lt;/FONT&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Here, AD team using -&lt;A href="https://sasviyxxx.xxxxweb.bp.com" target="_blank"&gt;https://sasviyxxx.xxxxglobal.xxxx.com&lt;/A&gt; at&amp;nbsp;&lt;FONT face="helvetica"&gt;&lt;STRONG&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Tenant URL&lt;/SPAN&gt;&amp;nbsp;&lt;/STRONG&gt;field in Azure portal and doing Test connection.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[sas@zneuxx34 sas_viya_playbook]$ ACCESS_TOKEN=`curl -skX POST "&lt;A href="https://sasviyxxx.xxxxweb.bp.com/SASLogon/oauth/token" target="_blank"&gt;https://sasviyxxx.xxxxweb.bp.com/SASLogon/oauth/token&lt;/A&gt;" \&lt;BR /&gt;-H "Content-Type: application/x-www-form-urlencoded" \&lt;BR /&gt;-d "grant_type=client_credentials" \&lt;BR /&gt;-u "&lt;FONT color="#3366FF"&gt;idp-client-id:idp-client-secret&lt;/FONT&gt;"| awk -F: '{print $2}'|awk -F\" '{print $2}'`; echo "The client access-token is: " ${ACCESS_TOKEN};&lt;BR /&gt;The client access-token is: eyJhbGciOifgfgffd......&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here I am getting Access token successfully.&lt;/P&gt;
&lt;P&gt;Note- I used idp-client-id &amp;amp; idp-client-secrent as it is &amp;amp; it worked fine. FYI I dont know old Client ID &amp;amp; secrets.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Viya SIte -&amp;nbsp;&lt;A href="https://sasviyxxx.xxxxweb.bp.com" target="_blank"&gt;https://sasviyxxx.xxxxglobal.xxxx.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;We don't have access to this site &amp;amp; as Azure AD team using above site at their end, I tried to register this site at my end.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But in the 3rd step only, I am not getting any access token as shown below.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;[sas@zneuxxxx34 sas_viya_playbook]$ ACCESS_TOKEN=`curl -skX POST "&lt;A href="https://sasviyxxx.xxxxweb.bp.com" target="_blank"&gt;https://sasviyxxx.xxxxglobal.xxxx.com&lt;/A&gt;/SASLogon/oauth/token" \&lt;BR /&gt;-H "Content-Type: application/x-www-form-urlencoded" \&lt;BR /&gt;-d "grant_type=client_credentials" \&lt;BR /&gt;-u "idp-client-id:idp-client-secret"| awk -F: '{print $2}'|awk -F\" '{print $2}'`; echo "The client access-token is: " ${ACCESS_TOKEN};&lt;BR /&gt;The client access-token is:&lt;BR /&gt;[sas@zneuxx34 sas_viya_playbook]$&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here No access token generated.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Fyi - we don't have access to -&amp;nbsp;&lt;A href="https://sasviyxxx.xxxxweb.bp.com" target="_blank"&gt;https://sasviyxxx.xxxxglobal.xxxx.com&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;When I tried to access above site, it is throwing error- Site cannot be reached &amp;amp; ....server IP address could not be found.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Query:&lt;/P&gt;
&lt;P&gt;How can I get the access token for ....global.xxx.com site which is used at Azure side for testing connectivity?&lt;/P&gt;
&lt;P&gt;Is this ...global.xxx.com should be accessible from my Virtaul machine then only I can get access token?&lt;/P&gt;
&lt;P&gt;I saw one email in which old Admin asked AD team to test the ..global.xxx.com site by providing access token in the email.And that's why I guess AD team is using Global website instead of ..xxxweb.xxx.com.&lt;/P&gt;
&lt;P&gt;Could you please help me on this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;RaviSPR&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2022 22:20:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849542#M1575</guid>
      <dc:creator>RaviSPR</dc:creator>
      <dc:date>2022-12-13T22:20:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849623#M1577</link>
      <description>"Note- I used idp-client-id &amp;amp; idp-client-secrent as it is &amp;amp; it worked fine. FYI I dont know old Client ID &amp;amp; secrets."&lt;BR /&gt;&lt;BR /&gt;It sounds like the client ID was created as "idp-client-id" and the secret "idp-client-secret", and you were able to successfully get a token.&lt;BR /&gt;&lt;BR /&gt;The question of which URL you should be using "web" versus "global" would be specific to your configuration and is not a function of SAS. I suspect if one isn't working you need to use the other one.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Dec 2022 13:45:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/849623#M1577</guid>
      <dc:creator>gwootton</dc:creator>
      <dc:date>2022-12-14T13:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to get Client ID &amp; Client Secret for setting up SCIM with SAS Viya</title>
      <link>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/856175#M1639</link>
      <description>&lt;P&gt;Thank You all.&lt;/P&gt;
&lt;P&gt;Yes.&amp;nbsp;&lt;SPAN&gt;idp-client-id &amp;amp; idp-client-secret were used as it is while creating tokens.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Finally the issue is resolved by updating the Certificate in Azure portal which was used for updating SSL certificates on SAS Viya.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 03:00:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Viya/How-to-get-Client-ID-amp-Client-Secret-for-setting-up-SCIM-with/m-p/856175#M1639</guid>
      <dc:creator>RaviSPR</dc:creator>
      <dc:date>2023-01-30T03:00:33Z</dc:date>
    </item>
  </channel>
</rss>

