-
Notifications
You must be signed in to change notification settings - Fork 541
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
User Credentials not Validated during SDNExpress Deployment #13
Comments
thanks for reporting this Jason. I will get this updated. |
Hello Jason, with the current design, VMMExpress does not validate the domain credential as part of the pre-check. It is responsibility of Admin to make sure that all the input parameters in fabricConfig file is correct. anyway, if the credentials are obsolete, the deployment will fail at the time of authentication. |
I think we should fix this, yes? |
@manishmsft -- Any progress here? Is this still an active issue? |
The issue is resolved in latest service template. Now we are validating the domain credentials provided in configuration file before triggering the deployment and the deployment does not start if the provided credential is incorrect. |
The issue is resolved in latest service template. Now we are validating the domain credentials provided in configuration file before triggering the deployment and the deployment does not start if the provided credential is incorrect. |
Script will rely on the service template for the domain password validation in the latest VMM SDN Express script. Closed it now. Thanks. |
I changed my domain account's password after it had expired and tried to re-run the SDNExpress scripts. The scripts failed to complete most notably because the Network Controller could not be accessed. I discovered later that I forgot to update my password in the configuration file (FabricConfig.psd1).
We should add a mechanism to either request new user credentials each time the script is run or at least validate that the current domain account is valid and usable. Right now, there is no intelligible error produced when the domain account referenced is incorrect.
The text was updated successfully, but these errors were encountered: