Save ERP Credenials in Vault Options

[PatrickGrub]

Details

The dummy plugin uses no credentials at the moment to communicate afterward with the ERP.

UseCase

• [x] User can save/change the credentials via a dialog where the password is hidden by clicking in the vault toolsbar "powerGate->Credentials". Material in project EMPL for the dialog
• [x] The ERP credentials should be saved in the Vault Options
  • [x] The password should be secure encrypted, see material in https://github.com/coolOrangeProjects/Metso-Minerals/issues/157
• [ ] The client must transfer in Connect-ERP the credentials
• [ ] The dummy plugin must read the User and Password from the request see Ticket 3797

Example for plugin read credentials

Extend powerGateServer config:

<behaviors>
      <serviceBehaviors>
        <behavior>
          <log4net />
          <serviceCredentials>
            <userNameAuthentication userNamePasswordValidationMode="Custom"
               customUserNamePasswordValidatorType="WCF_UserAuthentication.UserAuthentication, WCF_UserAuthentication, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/> 
          </serviceCredentials> 
        </behavior>
      </serviceBehaviors>
</behaviors>

Im Plugin ist es zu erweitern, das wird für jeden Service verwendet:

using System;
using System.IdentityModel.Selectors;
using System.IdentityModel.Tokens;

namespace WCF_UserAuthentication
{
  public class UserAuthentication : UserNamePasswordValidator
  {
    public override void Validate(string userName, string password)
    {
      if (userName == null || null == password)
        throw new ArgumentNullException();
      if (!(userName == "coolOrange") || !(password == "coo!Orange"))
        throw new SecurityTokenException("Unknown Username or Password");
    }
  }
}

[manfredmalleier]

Functionality implemented in Metso #157:

• A credentials dialog with code-behind
• A C# project for encryption and decryption of the ERP credentials.
  • The principle is documented here
  • The usage of the library in code is here

[PatrickGrub]

@kevinhallerCO this issue should be planned on my site since its very powerful and flexible for endcustomers, it will take about 4 hours.

[kevinhallerCO]

@PatrickGrub planned for the 28th. January for now (if there should be more urgent matters, we'll re-schedual this issue)