This post is part of the Enabling Secure Connection for Web Services series.

There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is a href=’There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is WSBindings.config; the second is the legacy endpoint config file, DynamicsGPLegacy.config which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.

There are three elements which need to be updated in the services node:

1. Change the behaviorConfiguration node from GPLegacyStaticMetadataBehavior to GPDynamicMetadataBehavior.
2. Change the bindingConfiguration node from BasicHttpBindingTarget to BasicHttpBindingTargetSSL.
3. Add a new https baseAddress line using the new port and the externally accessible DNS hostname:
   <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/DynamicsGPWebServices"/>

   <services>
      <service name="Microsoft.Dynamics.GP.WebServices.LegacyContract.DynamicsGP" behaviorConfiguration="GPDynamicMetadataBehavior">
        <endpoint address="Mex" name="http" binding="customBinding" bindingConfiguration="CustomBinding" contract="IMetadataExchange"/>
        <endpoint address="DynamicsGPService.asmx" name="LegacyDynamicsGP" binding="basicHttpBinding" bindingConfiguration="BasicHttpBindingTargetSSL" contract="Microsoft.Dynamics.GP.WebServices.LegacyContract.IGPServicesLegacy"/>
        <host>
          <baseAddresses>
            <add baseAddress="http://SERVER:48620/DynamicsGPWebServices"/>
            <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/DynamicsGPWebServices"/>
          </baseAddresses>
        </host>
      </service>
    </services>

Continue reading “Enabling Secure Connection for Web Services: Update Legacy Endpoint”

This post is part of the Enabling Secure Connection for Web Services series.

There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is WSBindings.config which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.

There are three sections of this config file which need to be amended, but before making any changes, take a backup of the entire file.

The first section is the basicHttpBinding section. Replicate the BasicHttpBindingTarget binding:

• Change the name by appending SSL
• Change the security mode to Transport

  <basicHttpBinding>
    <binding name="BasicHttpBindingTarget" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">
      <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
      <security mode="TransportCredentialOnly">
        <transport clientCredentialType="Ntlm"/>
      </security>
    </binding>
    <binding name="BasicHttpBindingTargetSSL" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">
      <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
      <security mode="Transport">
        <transport clientCredentialType="Ntlm"/>
      </security>
    </binding>
  </basicHttpBinding>

Continue reading “Enabling Secure Connection for Web Services: Update Bindings”

This post is part of the Enabling Secure Connection for Web Services series.

The first step in enabling a secure connection for web services, is to bind the certificate to the port which will be used for secure access. As mentioned in the last post, I am using port 48666.

There are two commands which need to be run to bind the certificate; these need to be run via an elevated command prompt.

The first command registers the certificate for the new port; there are three parameters (highlighted) which need to be changed in the command:

1. Port
2. certhas which is the certificate thumbnail
3. appid which is an arbitrary GUID; I generated a GUID using the SQL Server NEWID() command

Continue reading “Enabling Secure Connection for Web Services: Update Certificate Binding”

This post is part of the Enabling Secure Connection for Web Services series.

Before we start making any configuration changes to the Web Services for Microsoft Dynamics GP, there is a couple of decisions to me made:

1. Decide which port is to be used. Web Services by default installs on port 48620; to enable a secure connection a different port must be used. You can use any available port; to keep clear of any other ports being used, the port I am using for this series is 48666.
2. Create an externally accessible hostname with associated certificate; I am not covering this area in this series, but Microsoft’s Dan Peltier did a recent post titled “DNS Overview for External Workflow 2.0 Email Notification Approval”.

Finally, make sure to backup all configuration files before any changes are made to allow for a rollback if necessary.

Microsoft Dynamics GP 2013 R2 saw the introduction of a new Workflow module which allows the approval of transactions and changes to master records. Each version of Dynamics GP since then has seen additional new functionality introduced.

I have done a fair bit of writing about Workflow since it’s introduction, both in the form of blog posts and also books, but I recently realised that one element I hadn’t written about was the enabling of a secure connection for Web Services.

Web Services for Microsoft Dynamics GP is used by Workflow for Email Notifications and Actions. The default installation of Web Services is suitable for approvals which take place within the Domain, but not for outside. This is because the default installation does not secure the connection to Web Services.

In this series, I am going to cover each of the steps required to change Web Services over to using a secure connection.

Enabling Secure Connection for Web Services
Before You Begin
Update Certificate Binding
Update Bindings
Update Legacy Endpoint
Update Native Endpoint
Update GP Workflow Service
Final Service Configuration
Configure Workflow Setup

MVP Shawn Dorward has recently been taking a look at the use of custom links in Microsoft Dynamics GP. This is an area of Dynamics GP which I have never written about and, while I’ve shown it to a few clients, I don’t think any of them are actually using it.

However, as the series from Shawn shows, custom links can actually be very useful.

The links below are to Shawn’s GP Life Hacks

Microsoft Dynamics GP Custom Link
Using Custom Links to Track Packages, Add Images and More
Adding Custom Links for Customers
Adding Custom Links for Checkbooks, Credit Cards and Currency
Adding Custom Links for Employees
Adding Custom Links for Inventory Items
Adding Custom Links for Vendors
Using Skype for Business from within Dynamics GP