Integrated security support for WW connector

https://schneiderampla.atlassian.net/browse/CE-2011

[System Info]
Ampla 7.3. 1.419

[Enhancement Request]
Currently, the WW Connector only accepts windows credentials with an explicitly defined user/password field.
The use of explicit password fields means that each time there is a configuration change, customer has to input these passwords into the importing project manually as per Ampla's security checks/restrictions where it invalidate explicitly defined passwords when the importing service account is different. The impact to customer is, verbatim:

"
Our Test Environment uses a different Service Account from our Production Environment.
When we export the Ampla project from TEST and import the project into PROD.
We’re afraid we will get an password encrypted using a different service account error message.
Changing the password in x5 locations for each Change Management (ie Ampla configuration change) will become painful.

Service Account Prod: SA-AMPLA-XXX-PROD
Service Account TEST: SA-AMPLA-XXX-TEST
Service Account for WW Connector: sa-auper-pasadmin

We have x5 Connections so the password would need updating in x5 locations, each is a x16 character complex password.
An extra x5 steps to be added to our migration from TEST to PROD procedure
"
They have had major issues where service accounts were locked out when the same service account was used across Test,Dev and Prod, so the policy now is to use separate service accounts, as per best practise.

One way to avoid the above cumbersome process would be for the WW Connector to provide Windows Integrated Security Authentication to overcome the above issue of having to update security at multiple locations.

WW SDK 2014 R2 SP1 seems to support integrated security: