web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP Web Client Installa...
Microsoft Dynamics GP (Archived)

GP Web Client Installation - External Wildcard certificate

(0) ShareShare
ReportReport
Posted on by Community Member

Doing the installation of the Web Client, for the session host machine (Single Machine) at the moment to select the successfully installed wildcard certificate *.domain.com;

I receive the message:  " * can NOT be in the host name".

Do I need a single security certificate? Wilcard certificates are not working with the application?

Thanks !

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    EFRAIN

    It is recommended to use third party external wild certificate with it but you need to install and configure certificates in IIS using sever certificates option in IIS  Manager. After configuration in IIS Manager the certificate will be populated in drop down in installation wizard with its name to select. If you don't have wild card external certificate you can create self signed certificate to use for the web client GP 2013 temporarily .

    Humayun

  • Community Member Profile Picture
    Community Member on at

    Hi Humayun, thanks for your answer.

    Let me clarify, the certificate was issued as *.mydomain.com from an external party.

    The certificate was installed and configured successfully in the server in the IIS Manager.

    Durin the installation of trhe web client,in the Screen "runtime Service URL" where the certificate is required, b/c in previous one screen were optional, is POPULATED in drop down, once selected I receive the error message:

    INVALID INFORMATION

    The Host name cannot contain special characters such as a asterisk(*).

    Click Ok and the installation can't continue.

    Not sure if it's a bug addressed in the SP1.

    EC

  • Steve Kubis Profile Picture
    Steve Kubis on at

    A wildcard certificate should be fine to use. When you purchased the wildcard certificate, you had to indicate what domain you wanted to use for the certificate. You didn't have to specify the "computer" part of the name, because it's a wildcard certificate. You need to supply that part of the name when you use the certificate.

    When you get to the point in the install where it's asking for the host name, you need to supply the name of the machine. The installer doesn't know the name, so it's supplying an asterisk (*) which is what you need to replace. If your machine is named "GPServer" then you'd have to enter the following for the host name:

    GPServer.domain.com

    You replace * with GPServer, and the .domain.com part must match what you specified when you purchased the wildcard certificate.

  • Community Member Profile Picture
    Community Member on at

    Thanks Steve,

    The install doesn't ask for teh host name, only makes the validation whrn the certificated is selected from the drilldown window, under host name in that screen if I change the asterisk for GPWeb for example, I receive the same error.

    EC

  • Steve Kubis Profile Picture
    Steve Kubis on at

    Is the value you see in the drop-down list *.mydomain.com?  In my experience with wildcard certificates, I've never had one that had special characters in the name of the certificate. The only place I've ever seen an asterisk is in the name of the "Issued To" value for the certificate.

    If you have special characters in the certificate name, then it's quite possible that this isn't supported by the installer.

  • Community Member Profile Picture
    Community Member on at

    Hi Steve,

    The answer is yes, that's the reason I believe could be a bug in the Installation Application

    EC

  • Suggested answer
    Steve Kubis Profile Picture
    Steve Kubis on at

    After discussing this with a few people, we've seen this issue before. You can't have special characters in the friendly name of the security certificate.

    However, it seems that you can change the friendly name of the security certificate to allow you to bypass this issue. It doesn't look to be the simplest process, but you should be able to do this.

    Basically, you need to use the Certificate Manager MMC to open the correct certificate on the machine, edit its properties (the friendly name) and then save the change. To access the certificate, begin following the procedure on page 36 of the Web Client Installation and Administration Guide. This will allow you to view the certificate. When you you get to step 8, you should see your wildcard certificate listed in thePersonal/Certificates node. Right-click your certificate and choose Properties. The first property of the General tab is the "Friendly name" value. You should be able to change it here to something that doesn't contain special characters. Then you can click OK and save your changes.

    Then try your installation again. You should see the new friendly name when you get to the step of selecting the security certificate for the runtime service.

  • Community Member Profile Picture
    Community Member on at

    Hi Steve,

    The friendly name doesn't change the * in the host name of the issued certificate.

    Let me replicate the scrren with the issue, (screenshot doesn't work here)

    <<Select a certificate to configure the service for SSL access (required)>>

    I select the certificate from a rolldown field: It shows the certificates for selection by FRIENDLY name: GPWEB

    Next to this field, under a display field named 'Host Name' shows:    *.mydomain.com, OU-Domain Control Validation

    Then I receice the screen error: INVALID INFORMATION: The Host name cannot contain special characters such as asterisk (*).

    EC

  • Verified answer
    Steve Kubis Profile Picture
    Steve Kubis on at

    Notice that the Host Name field is editable. You must change the name by replacing the asterisk with the the actual machine name. If the machine is named "GPSERVER", then you would replace the asterist with gpserver, so the value in the field is:

    gpserver.mydomain.com

    You probably want to get rid of the other stuff at the end of the name, since that's not part of the host name.

    That's the original answer that was provided earlier in the thread. With a wildcard certificate, you as the person installing, must replace the asterisk with the machine name. The installer can't get the name from the certificate, because the machine name is never in a wildcard certificate.

    Replace the asterisk with the machine name, get rid of the extra stuff (the comma and other values) at the end of the name, and you should be able to continue.

  • Jonathan Fear Profile Picture
    Jonathan Fear on at

    Steve is correct. This isn't a bug as the cert should not have special characters in it.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans