About kkhelif

kkhelif · ‎10-22-2019

I have a track open and will update this thread once a solution is found. Thought someone might have had the same issue already.

kkhelif · ‎10-22-2019

Hi, I recently updated our SAS VIYA Deployment to add SAS/Access Interface to PC file, everything went successful except the license update didn't take and I am having issues doing an excel import even though the application added it successfully. I did a manual update on the license using ./Setup.bat -update-license but still doesn't update the license. When I try to view the license info in Environment Manager it says no licenses were found. Any ideas guys? Thanks

kkhelif · ‎02-23-2018

So I finally got it working again after upgrade and the documentation link is not even close to what we have. We use SPN/Kerberos/Keytab So here are the files I ended up modifying as they got overwritten and even the folder content got overwritten. \SAS\Config\Lev1\Web\WebAppServer\SASServer1_1\conf\Catalina\localhost\SASLogon.xml \SAS\Config\Lev1\Web\WebAppServer\SASServer1_1\conf\jaas.config krb5.ini was deleted from the directory structure and I have done the same for SASServr2_1 andASServer12_1 Thanks to all that responded.

kkhelif · ‎02-23-2018

Our Production environment is not upgraded yet.. I can look at that and compare. We did take a snapshot of all 3 tiers in DEV before upgrade. I will try to look at the differences

kkhelif · ‎02-23-2018

Our SSO/IWA Thanks guys for the links I already looked at those. our HTTPS work but we get the login screen now instead of using windows authentication and no Logon. I should have written down all the files we modified for Single Sign on. I am sure they got all overwritten with the M5 upgrade.

kkhelif · ‎02-23-2018

Hi all, We just finished upgrading our SAS tiers to 9.4 M5 and we lost our SSO. We get a logon page displayed now even though we had it configured prior to this upgrade. Does anybody know what config files got overwritten with the new ones. I remember we did a whole bunch way back. We have Meta and Mid on one server - OA/Compute on another server and VA/Compute on another Thanks

kkhelif · ‎12-12-2014

Dreamer, I have implemented the webpart for SharePoint in our agency and it took awhile to get it working. Make sure you installed the WCF web service and make sure you can call it using http://yourSASApplicationServer/SASWebPartsServices and this is what it looks like There are limitations on what you can do with the webpart as we scratched the whole project and went with Information Delivery Portal. You can do a lot more with Dashboards and Webreports and Stored processes than you can do with the Sharepoinit Webpart for SAS. * Also you can you use this link for diagnostics once you have everything working and your webpart is installed in your site collection. http://YourSharepointWebApp/_Layouts/SAS.Webparts/Diagnostics.aspx (I am assuming you left the default names and of course you need to change where it says (YourSharepointWebApp) with your Web application on sharepoint where the webpart is. Depending if you are activating the feature to several web apps or not. The aspx will help you determine where you went wrong and of course looking at your IIS log files on SharePoint and your log files for the web application itself where the webpart needs to be activated. Here is a shot of what a successful Diagnostics look like. Hope that helps and good luck.

kkhelif · ‎11-24-2014

try to hit one of your web applications and take a look at your server.log.

kkhelif · ‎11-24-2014

25 minutes max.

kkhelif · ‎11-14-2014

We implemented SSO for our IDP environment and it works great. The hardest part is to get your Kerberos settings correct the rest is not a big deal. hope that helps.

kkhelif · ‎10-02-2014

Make sure your Kerberos is working properly first in order to get the rest of the document working. First half of single sign on is the Kerberos and the keytab section. The rest is pretty straight forward. Good luck.

kkhelif · ‎10-02-2014

We integrated the AD Import that SAS offers with our Domain Controller and we schedule a job to run the script in SAS and does a dump from our LDAP/AD to SAS Metadata. Hope that helps.

kkhelif · ‎10-02-2014

Allan, If you ever used the AD Import for SAS. Make your change through that script and you're good to go. Thanks

Online Status	Offline
Date Last Visited	‎01-05-2023 12:57 PM

Re: SAS VIYA License fails to update

SAS VIYA License fails to update

Re: SSO after Upgrade to 9.4 M5

Re: SSO after Upgrade to 9.4 M5

Re: SSO after Upgrade to 9.4 M5

SSO after Upgrade to 9.4 M5

Re: SAS Web part for SharePoint

Re: Web Server start up time

Re: Web Server start up time

Re: Can i send user credentials in URL and avoid Log-in in SAS-Portal

SSO after Upgrade to 9.4 M5

Re: LDAP / AD group implementation on Windows

Re: SAS VIYA License fails to update

SAS VIYA License fails to update

Re: SSO after Upgrade to 9.4 M5

Re: SSO after Upgrade to 9.4 M5

Re: SSO after Upgrade to 9.4 M5

SSO after Upgrade to 9.4 M5

Re: SAS Web part for SharePoint

Re: Web Server start up time

Re: Web Server start up time

Re: Can i send user credentials in URL and avoid Log-in in SAS-Portal

Re: How to deploy web single sign-on for SAS EM in SAS 9.3?

Re: LDAP / AD group implementation on Windows

Re: How to search and change multiple user accounts

SAS Inner Circle Panel