-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for AAD username and password login #60
Labels
Milestone
Comments
This issue is idle because it has been open for 14 days with no activity. |
dzsquared
added
enhancement
New feature or request
and removed
need-to-triage
Requires investigation
labels
Jan 5, 2022
+1 to support ADD integrate login. |
This issue is idle because it has been open for 14 days with no activity. |
please keep open |
This issue is idle because it has been open for 14 days with no activity. |
Support for this is added in v2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The underlying SQLCMD tool allows for login to SQL Server by using an AAD username and password combination or even doing integrated login. This is currently not supported by the GitHub sql-action, since the -G switch is not used for AAD login.
I am currently working on a fully automated setup of an Azure SQL Server database fronted by a web app. Code for this can be found at: https://github.com/Azure-Samples/app-service-networking-samples
However I am bumping in the following restrictions for fully automating this flow:
I tried using:
However, the AUTHENTICATION = ActiveDirectoryPassword gets ignored.
On execution I get a 'Failed to add firewall rule', from sqlutils.ts file. However, there the login is done without the -G switch for SQLCMD and hence failing for AAD accounts.
Could be that this same issue exists deeper in the code on execution of the actual SQL command, currently I get a failure on FW settings.
Additionally making this integrated AAD login would be nice as well for people wanting to use account of the runner for log in.
The text was updated successfully, but these errors were encountered: