Architecting, installing and maintaining your SAS environment

DI Studio, SASApp access problem

Accepted Solution Solved
Reply
New Contributor
Posts: 2
Accepted Solution

DI Studio, SASApp access problem

Hi,

 

I'm ussing SAS DI 4.9 in a virtual server. I have defined throught SAS MC differents users with differents grants.

I have no had problem to open SAS DI studio, create folders, jobs or other tasks but when i try define a new library and i click to browse and define the path, the system ask me again for my credentials.

When i put the credentials the system give me the a message "Specify a valid user Id and password" and not allow me continue.

I know that the user is created in my SO and is defined in the SAS system with valid credentials, someone could help me to identify what am i doing wrong?

 


Accepted Solutions
Solution
‎12-14-2016 02:15 AM
New Contributor
Posts: 2

Re: DI Studio, SASApp access problem

Posted in reply to JuanS_OCS

Thank you for your answer,

 

 

Finally I've been able to solve the problem by changing the Security package in the local Workspace server to Kerberos. Even so I can't understand why it doesn't works by user and pasword but is enough by the momment.

 

Aitor

View solution in original post


All Replies
Super User
Posts: 5,426

Re: DI Studio, SASApp access problem

So it seems that your Metadata authorization works OK. But there's something that is not working with the server host credentials. How did you verify that user is defined with valid credentials?
Data never sleeps
Trusted Advisor
Posts: 1,312

Re: DI Studio, SASApp access problem

Hello,

Are you also able to run a SAS job from DI studio?
I wonder if your workspace is configured to authenticate with SAS token authentication. If so, that might explain already a lot.

Thank you in advance,
Best regards,
Juan
Solution
‎12-14-2016 02:15 AM
New Contributor
Posts: 2

Re: DI Studio, SASApp access problem

Posted in reply to JuanS_OCS

Thank you for your answer,

 

 

Finally I've been able to solve the problem by changing the Security package in the local Workspace server to Kerberos. Even so I can't understand why it doesn't works by user and pasword but is enough by the momment.

 

Aitor

☑ This topic is solved.

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

Discussion stats
  • 3 replies
  • 280 views
  • 0 likes
  • 3 in conversation