You are viewing limited content. For full access, please sign in.

Question

Question

Notification Configuration Utility

Forms Version 11
Updated December 7, 2021
asked on December 7, 2021

I was upgrading my Forms 11 with the latest update and the Notification Configuration Utility popped up.  This is what I saw:

It is missing the certificate which is in IIS and bound to port 443.  I'm not able to find any instructions on how to get my certificate added to this utility.

If I deselect "Use TLS" I can complete the upgrade and then go into formsconfig and select it under Notification Service.

Is this going to be a problem?  Why doesn't my certificate show up?

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on December 7, 2021

Hi Craig,

The Notification Configuration Utility's purpose is to provide a GUI to bind a certificate to port 8181. Selecting "Use TLS" in FormsConfig changes the notification service endpoints from http to https but does not bind the certificate necessary for https to work to port 8181.

I believe the utility is looking under the "Local Machine\Personal" certificate store for valid certificates. If your cert is in a different cert store, like "Local Machine\Web Hosting" I don't think it will appear in the utility's list.

If this is the case, you can use the original command line method outlined in Configuring Notification Service When Using TLS.

  1. Open Notepad or equivalent text editor
  2. Use https://www.guidgenerator.com/ to generate a GUID with braces and hyphens. Copy to Notepad.
  3. Get the thumbprint of your certificate, copy to Notepad, remove any spaces present, and ensure there are no invisible leading or trailing characters. 
  4. In Notepad, construct the following command with single quotes around the thumbprint and GUID values: 
    netsh http add sslcert ipport=0.0.0.0:8181 certhash='$yourCertThumbprint' appid='$yourGUID'

    Which should come out looking like:

    netsh http add sslcert ipport=0.0.0.0:8181 certhash='84f21326545445e808e17e0e00b72ca563e45332' appid='{cc9d6d47-3533-4281-9302-3965e71c06d3}'

  5. Run the command in PowerShell (not CMD) and then verify it appears with "netsh http show sslcert":

 

0 0
replied on December 7, 2021 • Show version history

Thanks Samuel

I did have to add the parameter for certstorename=WebHosting to the command for it to find the certificate and finally work.

netsh http add sslcert ipport=0.0.0.0:8181 certstorename=WebHosting certhash='84f21326545445e808e17e0e00b72ca563e45332' appid='{cc9d6d47-3533-4281-9302-3965e71c06d3}'
1 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...