Hello @cjsummers,
do you already have any database-based library on your SAS metadata or autoexec file?
BTW: I recommend you to use the autoexec_usermods.cfg file, instead of the autoexec.cfg
If a user is not connecting to the database, and is complaining about credentials, it would be either a problem of the credentials or the configuration of the authentication domain (for clarification purposes, let's focus on it, and let's forget about the autoexec configuration, you can comment any line you have on the autoexec)
Check that you can connect with the user to the database
Is the database connection ODBC/OLEDB, or just using the DB driver?
Do you have the SAS/ACCESS license to that database?
Do you have the DB connection created on your SAS compute server (in the OS? If ODBC, you need an ODBC connection, if you have a direct DB connection, you will need the client driver for that DB and to create the connection. Then, test the connection with the credentials you expect.
If everything OK till now, you can proceed with the configuration in SAS:
Create the DB Server definition (pointing to the server - SAS compute - where you created the DB connection in the OS)
Create the DB server connection (using the DB1Auth authentication domain)
Create the SAS usergroup, including your users as members and the DB credentials on the Account tab (also password ant the DB1Auth authentication domain)
Create the SAS library, assigning it to a SASApp, and selecting the DB Connection, and selecting the user account you will use (the one set on the usergroup)
(sometimes needed) Refresh/Restart Object spawner related to that SASApp
You can try to register some tables, to test the connection from SAS.
... View more