BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
AnnLyn
Fluorite | Level 6

Hi,

 

we have users who has deleted shared libraries. How can I secure the libraries and the users still be able to manage eg. delete and add  tables metadata and physically? We are running Sas 9.4 m8 standard. 

thanks in advance. 

regards,

Ann

1 ACCEPTED SOLUTION

Accepted Solutions
Patrick
Opal | Level 21

@AnnLyn wrote:
I know that we should define a ACT but is it possible to secure library and the users still have write and delete access to data below.

Assuming you're talking about SAS metadata:

If you don't have a security model that uses ACT's then it feels this model needs some improvement. 

You could definitely secure the library metadata from deletion while still allowing to register/modify table metadata for this library. Easiest would be to store the library metadata object in a different folder. 

Having said that: In a prod environment "normal" users should likely not be allowed to modify metadata at all. In a DEV environment: I'm of the opinion that developers need to take some responsibility and that admins shouldn't secure things too much as it can complicate justified developments activities. If there are developers who create "a mess" then this needs eventually to be addressed via training instead of tightened security. 

View solution in original post

4 REPLIES 4
AnnLyn
Fluorite | Level 6
I know that we should define a ACT but is it possible to secure library and the users still have write and delete access to data below.
Patrick
Opal | Level 21

@AnnLyn wrote:
I know that we should define a ACT but is it possible to secure library and the users still have write and delete access to data below.

Assuming you're talking about SAS metadata:

If you don't have a security model that uses ACT's then it feels this model needs some improvement. 

You could definitely secure the library metadata from deletion while still allowing to register/modify table metadata for this library. Easiest would be to store the library metadata object in a different folder. 

Having said that: In a prod environment "normal" users should likely not be allowed to modify metadata at all. In a DEV environment: I'm of the opinion that developers need to take some responsibility and that admins shouldn't secure things too much as it can complicate justified developments activities. If there are developers who create "a mess" then this needs eventually to be addressed via training instead of tightened security. 

AnnLyn
Fluorite | Level 6
They delete metadata libraries not physically.

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
  • 4 replies
  • 1251 views
  • 1 like
  • 3 in conversation