About PaulHomes

PaulHomes · ‎08-21-2016

No problem Mark. Glad to hear it's resolved. Thanks for marking the post as solved too.

PaulHomes · ‎08-21-2016

Not sure if the patch has been rolled out yet, but I just got the HTTP 500 error again (it's Monday morning in Australia).

PaulHomes · ‎08-19-2016

Is the logged password {SAS002}B6535B5C02BB1BC110FD31944FC989D3 by any chance? If so, that's the pwencoded version of 8 asterisks: proc pwencode in='********'; run; ... which indicates the metadata query is not being given the real encoded password by the metadata server. I'm guessing that the user Mark has user administration capabilities being a member of the Metadata Server: Unrestricted role or the Metadata Server: User Administration role - possibly via SAS Administrators group membership. Is this correct? Someone who is a user administrator has the ability to see all logins and so is restricted from fetching real passwords from metadata. Does it work when you try it a normal non-administrative user? Your code works for me when it is not run as a user admin (and no cache clearing is required). BTW what are you using this password for? If it's on a libname statement have you consider using the authdomain option and let SAS find the appropriate login (and if there are multiple logins available it will include logic to pick the one closest to the user in their identity hierarchy which the code above does not). See http://blogs.sas.com/content/sasdummy/2010/11/23/five-strategies-to-eliminate-passwords-from-your-sas-programs/

PaulHomes · ‎08-19-2016

This is great!

PaulHomes · ‎08-19-2016

Have you tried this? -authpd (ADIR:mydomain LDAP:mycompany.com) For more info see the documentation for the AUTHPROVIDERDOMAIN System Option.

PaulHomes · ‎08-19-2016

Are you running that second query in the same SAS session? Have you tried running it in a new session? Do you still get the old encoded password? The metadata query functions cache metadata. I haven't tested to see if it caches across data step boundaries, but if you find that running the query in a new session returns the new encoded password then you might want to look at the METADATA_PURGE function to clear the cache before your second query.

PaulHomes · ‎08-19-2016

Hi Ronan, not sure if you saw the ValidateServer command line tool in the SAS Platform Object Framework. I can't find the documentation link for it but there is a note about it: SAS Usage Note 42523: ValidateServer utility to check availability of SAS® 9.2 Business Intelligence servers. The note is about SAS 9.2 but it's still there in SAS 9.4 M3 ($SASHOME/SASPlatformObjectFramework/9.4/ValidateServer).

PaulHomes · ‎08-18-2016

I mean that you could consider shifting the burden of authenticating users across multiple providers from the SAS platform layer to the operating system platform layer. If you can configure the UNIX server, where your metadata server runs, to authenticate against multiple providers (and it is appropriately aligned with your IT security policies) then SAS can be configured for simple host authentication. An example could be using SSSD with multiple domains. Another possibility with VA is to shift the authentication to the mid-tier, where there are many authentication configuration options, then use (Trusted) Web Authentication possibly in combination with SAS Token Authenticaiton. Have a read through the Authentication Mechanisms section of the SAS 9.4 Intelligence Platform: Security Administration Guide for more background. You may also find the following papers and resources provide you with more ideas: SAS Global Forum 2014 Paper: Advanced Security Configuration Options for SAS® 9.4 Web Applications and Mobile Devices by Heesun Park (SAS Institute) SAS Global Forum 2014 Paper: An Advanced Fallback Authentication Framework for SAS® 9.4 and SAS® Visual Analytics by Zhiyong Li &Mike Roda (SAS Institute) The SAS Web Server Authentication and Web Authentication sections in the SAS 9.4 Intelligence Platform: Middle-Tier Administration Guide As an example of the flexibility that mid-tier authentication can provide SAS Visual Analytics Guest Access with IWA Fallback Since there are lots of options around authentication, without an understanding of your environment, SAS product mix, and business requirements it is hard to give specific advice. I would suggest contacting SAS Professional Services or a SAS Partner in your local region if you need more in-depth assistance.

PaulHomes · ‎08-18-2016

I would also suggest you look into SAS Environment Manager where you can have alerts that notify people when they get triggered. See the Working with Resource Alerts section in the SAS Environment Manager 2.5: User's Guide. You might also want to look at the Service Architecture Alert Definitions appendix for some examples of the alerts you get when you enable the SAS Environment Manager Service Architecture. It includes server/service and spawner availability alerts and many more.

PaulHomes · ‎08-18-2016

See the How to Configure Direct LDAP Authentication, Multiple LDAP Servers section in the SAS 9.4 Intelligence Platform: Security Administration Guide. You could also talk to your sysadmin about the possibility of configuring your UNIX platform for authentication against multiple providers and just leave SAS to do host authentication.

PaulHomes · ‎08-10-2016

I'm not sure if this is still an issue for you? It looks like you posted it in June but I only got my subscription email alert about it last night! 🙂 From your code, I'm assuming you are running your metadata server on port 8000? The SAS Metadata Server itself does not support JDBC. You need to connect to either a SAS Workspace Server or a SAS/SHARE server for a JDBC connection. However, the SAS Metadata Server can be used to find those servers. I'm assuming that is what you want to do? You'll find several JDBC examples for various different scenarios in the SAS 9.4 Integration Technologies: Java Client Developer's Guide, but since you mentioned using a metadata server I'd suggest you start with the example code in Connecting with Server Attributes Read from a SAS Metadata Server.

PaulHomes · ‎08-06-2016

It depends. Workspace Servers are managed by the Object Spawner. Have a read of the pages mentioned above, especially the SAS Management Console page regarding the Server Manager Object Spawner actions: Stop, Quiesce, Refresh Spawner, and Refresh Application Server. You also have the option to stop individual workspace server processes by navigating Server Manager > SAS Application Server > Logical Workpace Server > Workspace Server > hostname, connecting to the hostname, expanding the host name and then perfoming actions on the individual processes under the host name. See Use SAS Management Console to Connect to Servers and Display Server Monitoring Information. Of course in a load-balanced clustered/grid environment things are a little more complex because you have multiple Object Spawners. You didn't say what type of SAS install you have?

PaulHomes · ‎08-06-2016

You have several choices: Log onto the server and use the ObjectSpawner.sh or ObjectSpawner.bat script - see Using Scripts to Operate SAS Servers Individually ... or use SAS Environment Manager - see Using SAS Environment Manager to Operate Servers ... or use SAS Management Console - see Use SAS Management Console to Operate the SAS Object Spawner or the SAS/CONNECT Spawner

PaulHomes · ‎08-02-2016

Following on from my comment the other day, here's an example of the export output generated by our free ACT Reviewer. It shows the SAS Administrator Settings ACT (from a SAS 9.2 environment) showing its definition (Permissions section), where it has been applied (Objects section), and how it has been protected (ACTs and ACEs sections).

PaulHomes · ‎08-02-2016

I use cron jobs on Linux to purges old log files using the find command with mtime and delete options. You should be able to do a similar thing on Windows with the appropriate commands. I saw a StackOverflow question with a few examples: http://stackoverflow.com/questions/51054/batch-file-to-delete-files-older-than-n-days Of course, you'd need to be careful (and have a backup handy) when testing that type of process to make sure it only deletes log files and only in the right locations. The following SAS note will be helpful in identifying those locations: SAS Usage Note 55426: Locating the log files for the SAS® 9.4 middle tier That's a pretty big gemfire log so as @SASKiwi points out you might want to look at the contents to see if there are any issues there.

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