topic Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas? in Administration and Deployment

How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Asif4862 — Tue, 14 Apr 2020 19:50:29 GMT

Hello All,

How I could check these internal id's adminowner, vatadm and vdbadm credentials in sas? Is there any web url or SAS application where I could test these id's credentials?

Thanks,
Asif

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

SASKiwi — Tue, 14 Apr 2020 20:35:59 GMT

You can do that in SAS Management Console.

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Asif4862 — Tue, 14 Apr 2020 20:38:17 GMT

I did try using SAS Management Console but no luck

Thanks,
Asif

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

SASKiwi — Tue, 14 Apr 2020 20:48:46 GMT

If they are not defined in User Manager in SMC then they don't exist as SAS-defined internal accounts - but please note SAS accounts are listed by their description so you have to check each of their accounts to see the actual user name.

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Asif4862 — Tue, 14 Apr 2020 20:52:26 GMT

FYI: I added one internal account adminowner using SAS Management Console. And I tried to login with that id adminowner but still not able to login using SAS Management Console.

Thanks,
Asif

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

SASKiwi — Tue, 14 Apr 2020 21:11:37 GMT

What metadata groups did you add for adminowner? At a minimum you would want the account in the SAS Administrators group.

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Asif4862 — Tue, 14 Apr 2020 21:20:19 GMT

Yes @SASKiwi, I assigned SAS Administrators group to this newly created internal id. But when I tried to logon using SAS Management Console this error msg appeared:

Error authenticating user adminowner in function LogonUser. Error 1326 (The user name or password is incorrect. ).
Access denied.
The application could not log on to the server "servername:8561". The user ID "adminowner" or the password is incorrect.

Thanks,
Asif

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

SASKiwi — Wed, 15 Apr 2020 01:44:54 GMT

@Asif4862 - Please check your SMC connection profile. If you are using an internal account this has to be used along with the password instead of selecting the Windows Authentication option.

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Kurt_Bremser — Wed, 15 Apr 2020 08:18:20 GMT

For purely internal user-IDs, you need to use the correct authentication domain, otherwise the metadata server will search the default authentication domain, which either queries the local operating system or a remote LDAP source.

So you need to use

username@saspw

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

Sajid01 — Wed, 22 Apr 2020 13:59:13 GMT

With this error in mind "Error authenticating user adminowner in function LogonUser. Error 1326 (The user name or password is incorrect. ) " , I suggest try changing the password.

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

JenniStephens — Thu, 29 Oct 2020 14:29:25 GMT

FYI these accounts you mentioned are postgreSQL database accounts for the SAS WIP Data Server.. They are not SAS Metadata internal accounts that you use to access Metadata or that you can adjust in Mgt Console. The system uses them to store information about the Web Applications and the only time you'd use the logins directly is if you are manually logging into postgreSQL to update a table (something you'd normally only do under the direction of SAS Tech Support or SAS Professional Services).

Re: How to check these internal id's adminowner, vatadm and vdbadm credentials in sas?

SASKiwi — Thu, 29 Oct 2020 21:36:53 GMT

@JenniStephens - Thanks for the correction.