Last year I posted some information about a new Metacoda Auth Domain Reviewer plug-in that was planned for Metacoda Plug-ins 6.1. That Auth Domain Reviewer is now available with the recent Metacoda Plug-ins 6.1 R1 release and you may notice that it looks a little different to the screenshots I posted back then … it now has a Libraries tab.
The Libraries tab as was added based on feedback we got during early access testing by customers. They told us they would like to be able to see, for a selected authentication domain, all of the SAS® software libraries registered in metadata that are associated with that auth domain. That sounded like a great idea so we added it!
Thanks to those customers that suggested it and please keep those suggestions coming!
If you’d like to try out the new Auth Domain Reviewer plug-in you can login and download Metacoda Plug-ins 6.1 R1 from the Metacoda Customer Portal. If you don’t yet have a Metacoda login you can register for a free 30 day evaluation license to try the plug-ins in your own SAS platform installation.
Update 05Mar2019: The Metadata Auth Domain Reviewer discussed in this blog post is now available with the Metacoda Plug-ins 6.1 R1 release, and also includes a new Libraries tab based on feedback from customers during early-access testing.
One of the new Metacoda Security Plug-ins features arriving in version 6.1 is the Auth Domain Reviewer. Like the other reviewers, this plug-in is used for investigating, documenting and testing how a SAS metadata security feature has been used within a particular SAS platform deployment. When I’m reviewing metadata security for a SAS platform I like to look at it from several different perspectives and authentication domains is one of them. I like to see:
- What authentication domains have been added beyond the initial DefaultAuth?
- How have they been used with respect to inbound logins?
- How have they been used with respect to outbound logins and providing shared credentials for database access?
- How have they been used with respect to 3rd party database system connections?
- Are there any unused ones, possibly added by accident, that can be cleaned up?
- Are there any seemingly duplicate ones that might be consolidated?
In the past it has been time-consuming to gather this information together, so this new plug-in Continue reading “Metacoda Auth Domain Reviewer”
When I apply a new SAS license (setinit) each year, sometime I forget to also update it in metadata. I might not even remember until I get an email from the SAS platform itself:
From: SAS Platform
Subject: SAS Product Expiration Notification
Your license for SAS product name on sas.example.com has expired. Please contact your on-site SAS support personnel to obtain your updated setinit information.
“on-site SAS support personnel” … hey that’s me! I feel embarrassed that I forgot … again!
So, what if you want to be a bit more proactive and double-check whether you have an up to date SAS setinit in metadata? Continue reading “Checking a SAS Setinit/License in Metadata”
A few days ago I installed SAS Management Console 9.4 M4 and Metacoda Plug-ins 6.0 R4 on a Microsoft Surface Pro running Windows 10. After launching SAS Management Console, and logging in, it looked very odd. All of the icons and text were very close together and the text was hard to read. Here’s a screenshot (the images on this page are automatically resized to fit in the column, but I have kept them at their original resolution so you can click on them if you want to see them full size for comparison) …
This Surface Pro machine has a HiDPI display with a resolution of 2736×1824 and is scaled by default in Windows 10 at 200%. I assumed that Continue reading “SAS Management Console on HiDPI Windows 10”
As someone who specialises in SAS® metadata security, I spend a lot of time using the Authorization tab in SAS Management Console. I also use Linux a great deal. When I run SAS Management Console on Linux, I’ve noticed that the check box background colours on the Authorization tab don’t render correctly (for me at least). I only ever see white background check boxes when I expect to also see green and gray ones: green indicating an ACT; white indicating an ACE; and gray indicating indirect. These colours are important indicators for the source of access controls so not being able to see them is a problem!
It occurred to me that I might be able to resolve this by specifying a Java System Property in the sasmc.ini file to change the Java Look & Feel.
I first tried changing the default look & feel (using ‑Dswing.defaultlaf) but that didn’t work. What did work is changing the default system look & feel (with ‑Dswing.systemlaf). Continue reading “Java Look & Feel with SAS Management Console on Linux”