<?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: Connect R Studio to CAS in Viya 3.5 Error Unauthorized in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/880861#M26799</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/214450"&gt;@joeFurbee&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for this. Even using another user results to the same issue.&lt;/P&gt;
&lt;P&gt;For now we prefer the username/password approach.&lt;/P&gt;
&lt;P&gt;Anything further we can check why we are encountering this authentication issue?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The user we are using is an LDAP user and we can successfully login to the Visual Interfaces and can run CAS commands inside SAS Studio but failing when connecting from inside R Studio using swat.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 15 Jun 2023 05:50:11 GMT</pubDate>
    <dc:creator>alko13</dc:creator>
    <dc:date>2023-06-15T05:50:11Z</dc:date>
    <item>
      <title>Connect R Studio to CAS in Viya 3.5 Error Unauthorized</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/879483#M26762</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are trying to connect R Studio from workstation (In Windows) to CAS in Viya 3.5 for the first time using SWAT package.&lt;/P&gt;
&lt;P&gt;When we try to run the command to connect it is failing with Unauthorized. Screenshot below:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alko13_0-1686112838402.png" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/84761iD9D7A3A115749FD5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alko13_0-1686112838402.png" alt="alko13_0-1686112838402.png" /&gt;&lt;/span&gt;&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;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;After Installing Certificate valid-ca.crt in Trusted Root Certification Authority of the workstation, , Windows system environment variables were also updated:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alko13_1-1686112838404.png" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/84762i8C1F4434F2EE6705/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alko13_1-1686112838404.png" alt="alko13_1-1686112838404.png" /&gt;&lt;/span&gt;&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;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;These are the Error logs seen from environment manager:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="alko13_2-1686112838456.png" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/84763iF10D1ABF0D71A9CF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="alko13_2-1686112838456.png" alt="alko13_2-1686112838456.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Please advice for possible remedies to this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 04:41:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/879483#M26762</guid>
      <dc:creator>alko13</dc:creator>
      <dc:date>2023-06-07T04:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: Connect R Studio to CAS in Viya 3.5 Error Unauthorized</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/879536#M26763</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/437099"&gt;@alko13&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&lt;A href="https://blogs.sas.com/content/sgf/2018/07/25/using-rstudio-with-sas-viya/" target="_self"&gt;Here's an article&lt;/A&gt; I wrote on connecting to SAS Viya from R Studio. From your screen shots I don't see anything you've done incorrectly. Are you able to try the connection with a different user?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can also try and use an access token (&lt;A href="https://blogs.sas.com/content/sgf/2023/02/07/authentication-to-sas-viya/" target="_self"&gt;instructions for generating an access token&lt;/A&gt;) to connect vs using the username/password.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2023 13:21:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/879536#M26763</guid>
      <dc:creator>joeFurbee</dc:creator>
      <dc:date>2023-06-07T13:21:22Z</dc:date>
    </item>
    <item>
      <title>Re: Connect R Studio to CAS in Viya 3.5 Error Unauthorized</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/880861#M26799</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/214450"&gt;@joeFurbee&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for this. Even using another user results to the same issue.&lt;/P&gt;
&lt;P&gt;For now we prefer the username/password approach.&lt;/P&gt;
&lt;P&gt;Anything further we can check why we are encountering this authentication issue?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The user we are using is an LDAP user and we can successfully login to the Visual Interfaces and can run CAS commands inside SAS Studio but failing when connecting from inside R Studio using swat.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 05:50:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Connect-R-Studio-to-CAS-in-Viya-3-5-Error-Unauthorized/m-p/880861#M26799</guid>
      <dc:creator>alko13</dc:creator>
      <dc:date>2023-06-15T05:50:11Z</dc:date>
    </item>
  </channel>
</rss>

