You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the latest SLES15SP1 image (suse:sles-15-sp1-basic:gen2:2020.02.26)
targetpw is set by default in /etc/sudoers
When you deploy the VM the user can use sudo without the need to enter a password:
azureuser ALL = (ALL) NOPASSWD: ALL
But when you reset the user password from the Portal, it change the setting so that the user is require to enter a password:
azureuser ALL = (ALL) ALL
Since targetpw is set on this image, the user is prompt for the targetuser password, if the targetuser password is not set then the user cannot use sudo.
Is there a reason why the extension reset those settings and request the user to enter a password when using sudo ?
The text was updated successfully, but these errors were encountered:
People are pinging me about this issue, so I am sharing my reply below for reference:
Different users have different expectations I think it is hard to implement a solution that would fit all.
For example would the extension remove the targetuser option, some could argue that the extension could be used to circumvent the security policy.
So to me the best option when using the SLES images is to set the root password after deploying the VM or if you prefer to use the user password instead of the target user password when using sudo to comment that option like you did.
That way you will be to reset the password from the Portal using the extension and still keep sudo access.
On the latest SLES15SP1 image (suse:sles-15-sp1-basic:gen2:2020.02.26)
targetpw is set by default in /etc/sudoers
When you deploy the VM the user can use sudo without the need to enter a password:
But when you reset the user password from the Portal, it change the setting so that the user is require to enter a password:
Since targetpw is set on this image, the user is prompt for the targetuser password, if the targetuser password is not set then the user cannot use sudo.
Is there a reason why the extension reset those settings and request the user to enter a password when using sudo ?
The text was updated successfully, but these errors were encountered: