support for user authentication without access to master db about sql-action HOT 7 CLOSED

Have submitted a PR for this! Hope it's OK!

from sql-action.

Hmm I redacted the username and server name in my post above but I used angle brackets so GitHub removed the word "redacted" entirely. Rest assured the user id is set in the connection string. :)

from sql-action.

Have updated to the latest version but still getting the same error. My action looks like this now:

 - name: Apply EF migration script
        uses: Azure/[email protected]
        with:
          connection-string: ${{ secrets.CONNECTIONSTRING_PUCKA }}
          sql-file: ./migrate.sql

from sql-action.

OK I have a theory.

When I created my Azure SQL user, I did it in my database like this:

CREATE USER [my-user] WITH PASSWORD = '...';
ALTER ROLE db_owner ADD MEMBER [my-user];

So the user exists in my database but does not correspond to a "login". It therefore has no access to the master db.

When you try to detect the client IP address, you're doing this:

await exec.exec(`"${sqlCmdPath}" -S ${serverName} -U "${connectionString.userId}" -P "${connectionString.password}" -Q "select getdate()"`

... which is trying to connect to my server, but not to my database. So I'm guessing it will try to connect to master and fail.

Can you use the full connection string in your command so that it connects to the database directly rather than to master?

from sql-action.

Or alternatively, could this line:

... have a -d "${connectionString.database}" parameter? My connection string says "Initial Catalog=..." but presumably "database' is the right property name for your connectionString object.

from sql-action.

This issue is idle because it has been open for 14 days with no activity.

from sql-action.

This was fixed in #104 and will be in the v2 release

from sql-action.