locked
UCMA 3.0 Microsoft.Rtc.Signaling.TlsFailureReason.IncorrectNameInRemoteCertificate RRS feed

  • Question

  • Hello everyone,

    Our company is developing a web application and one of its features is showing presence status of company users. We are connected through VPN to that company, they provided us one certificate and lync client is working like a charm. The problem is when we try to run SubscribePresence sample provided by UCMA 3.0 we always get the same error:

    Microsoft.Rtc.Signaling.TlsFailureException:  The target principal name is incorrect.

    FailureReason: Microsoft.Rtc.Signaling.TlsFailureReason.IncorrectNameInRemoteCertificate

    What could cause this error and how can we correct it?

    Thanks in advance, best regards.

    Monday, June 6, 2011 11:29 AM

Answers

  • The certificate used to authenticate clients is not what you need to use for UCMA applications running on a server.  The certificate on the server running the UCMA app needs to be in the Machine certificate store in the "Personal" folder.  That cert needs to have the SAN set to the FQDN of the server where the app is running and needs to be trusted by the Lync server and the "local" app server.  This might require you to install the root certificate for the certificate authority that issued the server cert if it is not one of the root authorities that comes pre-populated in Windows Server.

     

     


    Oscar Newkerk

    Oscarnew Consulting

    Tuesday, June 7, 2011 1:10 AM