Skip to main content

Providing access to Authorization Manager Plug in SAS

There are times where SAS Admins need to provide access to specific plugins in SAS Management Console. Here I am going to cover providing access to Authorization Manager Plug in using SAS Management console 9.2. The scenario here is the user named Robert needs access to Authorization Manager Plug in alone. He want to do migrate ACT from one environment to other.

Note: This scenario can done in SAS Management Console 9.3 and 9.4.

What should be done?
First you should create a new Group and a new Role. Yes, a new group is needed to hold the list of users who need access to Authorization Manager Plug in alone. It is always good to have separate group for a separate role. It makes your life easier when it comes to maintenance.

Let’s say the group name is Authorization Manager group. Then a new Role should be created which gives access only to Authorization Manager Plug in. There will be many default roles available but it is always better to create a new one.

Steps

Step 1: Creating a new Group
To create a new groups click on User Manager Plug-in and add new group. You will get a similar window like above. You can give whatever name you need. It is best to follow your industry naming convention.

Step 2: Adding the existing user to Authorization Manager group
You need to add the user in members tab in the newly created group. In our scenario Robert is the user who needs access to plugin. So I am adding him as a member of the group.

Step 3: Creating a new role for Authorization Manager plugin
Here I am creating  new role. New role can be created using User Manager Plug in in SAS Management Console. I am naming the role as Authorization plugin only.

Step 4: Adding Members to the Role
Here you will get the same screen as Step:2. In members we need to add the group "Authorization Manager group" which I created now. Member should be Authorization Manger group as Robert is member of that group.

Alternatively, you can add 'Robert' directly as member of this role. I am adding him to the group because it will be easy for me to add if new users needs the same access.

Step 5: Plug-in
In the Capabilities tab, you can decide what plug-in can the user see in their client tool. Robert needs Authorization Manger which is part of SAS Management Console. You can find it under Plug-ins. I am checking only the Authorization Manager. So here is what Robert can see in his SAS Management Console.


Robert can only able to view Authorization Manager plugin.

Comments

Popular posts from this blog

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...