BookmarkSubscribeRSS Feed
pavelr
Obsidian | Level 7

When I add a Custom Group access control for a caslib using code I get a warning icon near that Custom Group in the "View Authorization" window (Environment Manager-Users-Data Sources-CASLIB-View Authorization) for that caslib. The Custom group exists. Why am I getting this warning (Alert) icon (a triangle with an !) ? The code looks like this:

proc cas;
accessControl.updSomeAcsCaslib /
acs={
{caslib="MYCASLIB",
identityType="group",
identity="My Custom Group",
permType="Grant",
permission="READINFO"}};
run;

quit;

9 REPLIES 9
gwootton
SAS Super FREQ
Is the custom group's ID also "My Custom Group" or just the name? You can check the ID by selecting the group in Environment Manager, or you can visit the /identities/groups?providerId=local REST endpoint for a list of custom groups and their IDs.
--
Greg Wootton | Principal Systems Technical Support Engineer
pavelr
Obsidian | Level 7

It's both the name and the ID. 

And the users of this custom group cannot access a caslib though access rules are there - only with this triangle alert. If I create the same rule manually - it works. What's wrong with creating these rules using accessControl action?

gwootton
SAS Super FREQ

The warning icon indicates the defined identity is not found. While Environment Manager will only let you select from a list, the code lets you specify any string so the discrepancy is likely with the group name you are providing.

 

The permission isn't working for the same reason, the rule is defined for a non-existent identity.

 

You may wish to use the sas-admin cli to check the name and ID of the group:

sas-admin identities list-groups
--
Greg Wootton | Principal Systems Technical Support Engineer
gwootton
SAS Super FREQ
You may wish to copy and paste the name from the sas-admin output or Environment Manager, it could be there are extra white space characters in your code or the group name causing the failure.
--
Greg Wootton | Principal Systems Technical Support Engineer
pavelr
Obsidian | Level 7

No there are no extra white space characters in the code. I literally copied the Custom Group ID from the Environment Manager and pasted it in the code. And got the same alert.

 

But it looks like the problem was found. When the group ID has white spaces, I get the alert. When group ID does not have white spaces - no alerts. But why is this? On the other Viya server there is no such problem with white spaces in a Custom Group  ID - no alerts. So, maybe there is some option in Viya that allows or disallows to use IDs with white spaces?

gwootton
SAS Super FREQ
I'm not aware of such an option. If you see this issue in one environment and not another, it sounds like this may be an issue that was corrected in an update.
--
Greg Wootton | Principal Systems Technical Support Engineer
pavelr
Obsidian | Level 7

If fact, I've just tested assigning caslib rules manually by: Edit Authorization - Add Identities. I select groups with white spaces in their IDs from the list (!) and it shows this alert - "The principal was not found".

 

We do not have this issue in other environment which is older than the problematic environment.

gwootton
SAS Super FREQ
I would recommend opening a technical support track then.
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 9 replies
  • 1746 views
  • 1 like
  • 2 in conversation