-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add windows authentication #285
Comments
Hi @dave-vogelaar, its been a few years now since I worked where this is used in production, but I believe this is already supported via DBATools underneath the collection - as long as your powershell session is authenticated, you can just omit the sql username and password and it will default to the Windows auth. So you just need to make sure the playbook is executing in the proper context and you're good to go. |
You can check the Ansible documentation on setting up Kerberos auth for WinRM here: https://docs.ansible.com/ansible/latest/os_guide/windows_winrm.html#inventory-options |
Thanks for the update! |
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
It appears that only sql authentication is allowed. Can windows authentication be enabled as a feature? Most places I have been are very leary of providing sql auth for higher privileged accounts.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Provide an ability to use a become in ansible playbook and leverage trusted authentication
The text was updated successfully, but these errors were encountered: