Architecting, installing and maintaining your SAS environment

Permissions issue - Setting up VA

Accepted Solution Solved
Reply
Frequent Contributor
Posts: 87
Accepted Solution

Permissions issue - Setting up VA

[ Edited ]

Hi all,

 

I'm trying to set up our SAS VA server, I think I'm nearly there but having a few frustrating issues, hope somebody can help. (Basically I'm way out of my depth)

 

If I log into the VA hub with the sasadm user it lets me in but won't allow me to access the sample data. I can see the data sources but it tells me its not avialble and to contact admisitrator. (I cant see the library I added at all though)

 

If I try to log in as a normal user I get a message saying that public users are not allowed to access, however I have granted every permission possible to the user under "groups and roles" in user manager.

 

I guess I'm missing something obvious, hoping someone can help Smiley Happy

 


Accepted Solutions
Solution
‎09-30-2016 05:16 AM
Super User
Posts: 6,946

Re: Permissions issue - Setting up VA


itchyeyeballs wrote:

Thank you,

 

I dont have access to those docs at the moment, (I'll contact my account rep to sort out).

 

I guess its probably related, I followed the advice in another post and tried to register and update tables in manage environment but got

 

"The user "SAS Administrator" could not log on to the server "SASApp - Logical Workspace Server". No valid identity could be found for the authentication domain "DefaultAuth"."

 



The SAS Administrator (sasadm@saspw) does not have a match in the operating system (by default). It only exists in SAS metadata.

Since the SASApp Workspace Server is started for each user individually, it needs an operating system account that provides permissions for creating the WORK directory, and a HOME location where a SASUSER library etc is created/found.

So you can't start a non-pooled wokspace server with sasadm@saspw.

You need to supply credentials that

- exist in the operating system

- have an entry in metadata where the operating system account ist stored in the "Accounts" tab in the SMC User Manager, with Authentication Domain "DefaultAuth"

 

The sasadm account is created solely for administration of metadata, not for working with SAS.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers

View solution in original post


All Replies
SAS Employee
Posts: 101

Re: Permissions issue - Setting up VA

Public user makes it sound like you're authenticating against the backend OS, but it's not looking up properly to a User in metadata (particularly one that's granted a Visual Analytics role)

The 'Adding Users' section of the Visual Analytics Administration Guide should give the right steps (both for which Visual Analytics groups you need membership too, and a link into the Intelligence Platform doc about adding users)

http://support.sas.com/documentation/solutions/va/73/en/vaag.pdf
Frequent Contributor
Posts: 87

Re: Permissions issue - Setting up VA

Thank you,

 

I dont have access to those docs at the moment, (I'll contact my account rep to sort out).

 

I guess its probably related, I followed the advice in another post and tried to register and update tables in manage environment but got

 

"The user "SAS Administrator" could not log on to the server "SASApp - Logical Workspace Server". No valid identity could be found for the authentication domain "DefaultAuth"."

 

Anything I should check? 

 

Back story - I'm not a tech, we have had SAS VA for 18 months but not implimented (bought but no budget for implimentation - dont ask!). I'm new to organisation and trying to build a case to get a budget by getting some real world demos up and running, have spent 3+ weeks working through install issues, feel like its very close but cant get past this problem.

 

 

Super User
Posts: 3,110

Re: Permissions issue - Setting up VA

Could it be that your sasadm account is not also set up as an OS user account (Windows / Unix?). It needs to be set up as an OS account to be able to logon to your SAS App server.

Frequent Contributor
Posts: 87

Re: Permissions issue - Setting up VA

Hi,
Its windows.
The account is set up in windows, it's the account I use to log into the VM that is running SAS
Really appreciate the help!
Super User
Posts: 3,110

Re: Permissions issue - Setting up VA

In that case check that the user account has "log on as batch job" permission for the SAS App server.

Solution
‎09-30-2016 05:16 AM
Super User
Posts: 6,946

Re: Permissions issue - Setting up VA


itchyeyeballs wrote:

Thank you,

 

I dont have access to those docs at the moment, (I'll contact my account rep to sort out).

 

I guess its probably related, I followed the advice in another post and tried to register and update tables in manage environment but got

 

"The user "SAS Administrator" could not log on to the server "SASApp - Logical Workspace Server". No valid identity could be found for the authentication domain "DefaultAuth"."

 



The SAS Administrator (sasadm@saspw) does not have a match in the operating system (by default). It only exists in SAS metadata.

Since the SASApp Workspace Server is started for each user individually, it needs an operating system account that provides permissions for creating the WORK directory, and a HOME location where a SASUSER library etc is created/found.

So you can't start a non-pooled wokspace server with sasadm@saspw.

You need to supply credentials that

- exist in the operating system

- have an entry in metadata where the operating system account ist stored in the "Accounts" tab in the SMC User Manager, with Authentication Domain "DefaultAuth"

 

The sasadm account is created solely for administration of metadata, not for working with SAS.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
Frequent Contributor
Posts: 87

Re: Permissions issue - Setting up VA

Thanks for the help guys,

 

I have a better idea now around where I was going wrong (especially whilst trying to use sasadm incorrectly). I have changed the permisions and now seem to be making some progress.

 

One of my problems is that we have 2 licence files, I can only find how to apply one at a time so some aspects of the functionality are not working, I'll contact SAS about that (unless anyone knows how to apply two sid files?)

☑ This topic is SOLVED.

Need further help from the community? Please ask a new question.

Discussion stats
  • 7 replies
  • 1305 views
  • 1 like
  • 4 in conversation