Create Login User
Description
The plugin is designed to create login user for the MSSQL Server. This plugin is only valid for SQL Server Authentication and not Windows Authentication.
Configurations
| No. | Field Name | Description |
|---|---|---|
| 1 | Step Name | Name of the step. This name has to be unique in a single workflow. |
| Connection: | ||
| 2 | Server Name | |
| 3 | Instance name | The instance name of MSSQL Server instance. One of the two fields Instance name or Port is mandatory. Only variables/static values are allowed. |
| 4 | Port | The port number of the MSSQL Server. One of the two fields Instance name or Port is mandatory. Only variables/static values are allowed. |
| 5 | Username | A username of the MSSQL Server. This field is mandatory. |
| Password | ||
| 6 | Checkbox: Accept Value as variable/static | Leave checkbox unchecked to accept Password value from a field in the previous steps of the stream using a drop down list. Else enable checkbox for Password field to appear as Text box. |
| 7 | Password | Provide the password of the username of MSSQL Server. Password is entered using a widget. The widget handles both Text Var(static value or environment variable) and Combo(drop down containing values from previous steps). This field is mandatory. If checkbox above is enabled Password field appears as Text box. Else if checkbox above is disabled Password field appears as a drop down to select fields from previous steps. |
| 8 | Other Connection Parameter | Specify multiple, semi-colon separated parameters other than the default connection parameters. Other connection parameters will be appended to the default connection parameters. Example of default connection parameters: Server Name, Password. Examples of other connection parameters: encrypt=false;trustServerCertificate=false |
| Button | ||
| 9 | Test Connection | Verifies whether the connection is established or not. NOTE: Test Connection button does not work for previous step fields. Test Connection button only works with static values and environment variables. |
| Input Fields: | ||
| 1 | NewUser | Name of the User which is to be created for login. |
| 2 | Password | Password given to the user. But it must have complex & fulfill windows policy. |
| 3 | Enforced Password Policy | Acceptable values are “Yes” or “No”. User can select appropriate value as per requirement (Password policy is as per windows password policy). When it is set to Yes, it is considered that the password is enforced as per the policy in the system. - When input to this field is provided as workflow variable or static value then, --> If Yes is selected, the below two fields are auto populated with Yes. However, they can be set to No also. --> If No is selected the below two fields are auto populated with No. - However, when values are chosen from drop down choosing a field from previous steps, it does not auto populate “Enforced password Expiration” and “User Must Change Password on First Login”. The default values are the same as this field or user can set these values manually. |
| 4 | Enforced password Expiration | It manages the lifespan of the password as per Windows policy. Acceptable values are “Yes” or “No”. Default value is set as the value in the field above “Enforced Password Policy”. - When input to this field is provided as workflow variable or static value - If Yes is set in this field the below field is auto populated with Yes. However, it can be set to No also. - If No is selected the below field is auto populated with No. Only NO is valid in this case. Setting to Yes would cause runtime error. - However, when values are chosen from drop down to choose a field from previous steps, it does not auto populate “User Must Change Password on First Login”. User needs to set Yes/No. - User Must Change Password at Next Login Acceptable values are “Yes” or “No”. When value is Yes it asks to user to change the password on the next login. - Default value is set as the value in the field above “Enforced Password Expiration”. If “Enforced Password Expiration” is No valid value is only No. If “Enforced Password Expiration” value is Yes both Yes and No are valid. - When it is set to blank, it is considered as “Yes” while executing the workflow. - If the value is taken from previous fields that are empty then the plugin considers the value as Yes. |
| Output Field | ||
| 1 | Result | The output field holds the result of successful plugin execution. |
| Error Handling | ||
| Refer Appendix 1: Error Handling in IT Plugins |