About PaulHomes

PaulHomes · ‎08-09-2018

I that case, if you are running SAS MC on a machine where you have successfully added the CA cert(s) into the SAS Private JRE Trusted CA Bundle then I would expect it to work. I just checked validating the SAS Content Server using SAS MC in my own environment where we have a chain (server>site-intermediate-CA>site-root-CA where both CA's are in the Trusted CA Bundle) and that validated ok: [10/08/18 9:59 AM] INFO: Starting simple validation for WebDAV server (level 1) - ping [10/08/18 9:59 AM] INFO: Ping successful! [10/08/18 9:59 AM] INFO: Starting extended validation for WebDAV server (level 1) - Making a connection [10/08/18 9:59 AM] INFO: Path: 'https://server.sub.example.com:8343/SASContentServer/repository/default/sasfolders/' [10/08/18 9:59 AM] INFO: Connection successful! [10/08/18 9:59 AM] INFO: Starting extended validation for WebDAV server (level 2) - WebDAV enabled [10/08/18 9:59 AM] INFO: Server is WebDAV enabled! [10/08/18 9:59 AM] INFO: Starting extended validation for WebDAV server (level 3) - Path existence [10/08/18 9:59 AM] INFO: Path exists! In my case I was running SAS Management Console (9.4 M5) on Windows verifying a SAS Content Server on Linux and so the SAS Deployment Manager had been previously used on both Linux and Windows to add the CA certs on both platforms. I would suggest you double check the CA(s) in your chain are present in your SAS Private JRE Trusted CA Bundle(s). I posted the method I use to confirm this in a blog post: Did I add that CA Certificate to the SAS Trusted CA Bundle? If that doesn't help locate the source of the problem then I would suggest contacting SAS Technical Support.

PaulHomes · ‎08-08-2018

Just to confirm, on which machines did you use SAS Deployment Manager to import your certs? Did it include the (client?) machine where you are running SAS Management Console to do the validation of the SAS Content Server?

PaulHomes · ‎08-02-2018

To launch SAS Workspace Servers using a service account instead of the requesting user account you can configure it for SAS Token Authentication - see SAS Token Authentication and How to Configure SAS Token Authentication in the SAS 9.4 Intelligence Platform: Administration Security Administration Guide.

PaulHomes · ‎08-01-2018

Nice find command. I like how UNIX and Linux, as with SAS, has several different ways of achieving an outcome. When I'm grepping files I often use the following command (which I find slightly easier to remember than the find/exec/grep combo): grep -FRIis --exclude=*.log hostname /opt/sas94/config/Lev1/ObjectSpawner/ F = fixed strings (not regex) R = recurse following symbolic links I = treat binary files as non-matching i = ignore case s = ignore nonexistent or unreadable files. The above also excludes log files which have many instances of host names in them.

PaulHomes · ‎07-31-2018

Ah .... I didn't realise you were looking for icons for the model types. I don't have an easy answer for that one. We use a mapping that we derived ourselves (referring to a mixture of public type icons and some of our own specific/generic icons). In terms of the display of icons for model types in SAS products, I can only think of 2 places where you would see them: metabrowse in DMS and the SAS Management Console Authorization Manager plug-in (Resource Management > By Type). The first use old DMS-style icons and the second uses a single generic icon. From my SAS/AF coding days, I vaguely remember the old DMS-style icons were in a SAS catalog somewhere.

PaulHomes · ‎07-31-2018

In that case I would grep the file system and search metadata for the old host name and see if there are any remnants. When I want to find something like this I use our Metacoda Metadata Explorer - use the Options button to 1) switch to searching all Model Types and 2) search All Character attributes - then type the old host name in the search field. Just be aware that the method it uses for searching can't look past the first TextPage of long text "V" length metadata attributes. If that doesn't help resolve it then perhaps SAS Tech Support might be able to assist further.

PaulHomes · ‎07-30-2018

Depending on your SAS architecture you may need to get your domain admins to configure the SAS Computer Tier machine(s) as Trusted for Delegation - see SAS and IWA: Two Hops

PaulHomes · ‎07-30-2018

Hi Bart, Did you see the SPWNNAME environment variable in ObjectSpawner.sh? Does it have the old or new name? I see it is passed to ObjectSpawner via the sasSpawnerCn command line option and wonder if that is used to lookup the object spawner metadata object (or it's connection) by name (as it looks from the query in the error you posted). If the Update Host Name References tool doesn't rename the metadata object then perhaps it doesn't change that environment variable either? Cheers Paul

PaulHomes · ‎07-26-2018

Isn't that just the way it works with non-distributed VA? The process you use to launch the server will block until someone shuts that server down. It could be a batch program launched in the background so it doesn't lock up an interactive session (DMS, EG, etc). If that's not preferred, have you looked into the alternative autoload option?

PaulHomes · ‎07-26-2018

Have you had a look at the SAS Deployment Manager log files to see if there are any additional error messages or clues? I just checked /home/sas/.SASAppData/SASDeploymentWizard/*.log and can see when I added my site CA certificates. Perhaps your log files have some helpful error messages?

PaulHomes · ‎07-26-2018

Have you seen this SAS blog post by Gilles Chrzaszcz? How LASR servers are started from SAS Visual Analytics Administrator Being on Windows yours is a non-distributed VA right? There's some sample code at the end of the post which uses proc vasmp serverwait after the libname statement to keep the server running.

PaulHomes · ‎07-23-2018

I just checked my notes and saw I had written: # Use SAS Deployment Manager to import our CA certificates into the trusted CA bundle. # Can only add one cert at a time. # Need to remove text descriptors from the .crt files before using SAS Deployment Manager (otherwise it complains about non-PEM encoding) ... this doesn't sound like the error you have having but I would look inside the PEM files to check they only have a -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- block and no text form of the certificate before/after the block.

PaulHomes · ‎07-23-2018

I forgot to add that the openssl x509 command is very useful in reviewing/checking the PEM files before you add them to the SAS Trusted CA Bundle. Check out the Examples section of the OpenSSL x509 man page for some examples command lines. BTW sometimes PEM files come with a text version embedded in them to make it easier for humans to read. I have found that some tools (can't remember if the SAS Deployment Manager is one of them) don't like this and so if I have problems I'll remove the additional text so that the PEM files only contain the -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- block(s).

PaulHomes · ‎07-23-2018

What method are you using to import your CA certs into the Trusted CA Bundle, and what commands are you using (if any)? Have you seen Manage Certificates in the Trusted CA Bundle Using the SAS Deployment Manager in the Encryption in SAS® 9.4 documentation? When SAS or third party software makes a TLS connection to a SAS server it needs to verify the certificate chain. If the server cert is signed by an intermediate CA and that intermediate CA's cert is signed by a root CA then the root CA and the intermediate CA certificates need to be found as trusted certs by the client. For SAS clients the Trusted CA Bundle is used. If you have site signed certs then you add your site CA certificate (and any site intermediate CA if used). If you have commercial CA signed certificates (e.g. DigiCert etc) where the commercial root CA cert is already present in the Trusted CA Bundle then you may only need to install any intermediate CA certificate (all the commercial CA certs I have used have had an intermediate CA). I sometimes forget whether I have added CA certificates to the Trusted CA Bundle and so wrote down some notes on what I do to check in this blog post: Did I add that CA Certificate to the SAS Trusted CA Bundle?

PaulHomes · ‎07-23-2018

Hi Frank, I don't remember having to override the icons for many public types so I just had a look at our SAS 9.4 M5 environment using the Metacoda Public Types Explorer and can only find 3 types without a DefaultIcon: Column hierarchy Decision Logic Service How many do you have with no DefaultIcon and which ones? Which SAS version and maintenance? I see a total of 191 public types in our SAS 9.4 M5 environment. How many do you have? I think the collection of public types will change depending on which SAS products and solutions you have installed (and versions of course). For example our SAS VA 7.4 (9.4 M4) has a total of 182 public types (and the same 3 public types with no DefaultIcon). Cheers Paul

Online Status	Offline
Date Last Visited	‎02-11-2025 08:08 PM