Environment:
- SharePoint 2013 Enterprise on premise, 2 Hyper-V VM servers (SharePoint and SQL)
- New Hyper-V VM with Workflow Manager running on it (running on a different Hyper-V host)
- Servers are Win Server 2012 or 2012 R2
Used Spencer Harbar's guide for installing and settting up WFM (http://www.harbar.net/articles/wfm2.aspx). Seemed to go well, had a couple of tries to get it right, between missing tweaks and mistyping names. Love VMs for the checkpoints!
Get down to the last step, creating the service connection, and continue to get "The root of the certificate chain is not a trusted root authority." Okay, get that since the cert was auto-generated by WFM install. But I've exported the key and, I believe, the root cert, from WFM and put them on my SP server. I've used the cert manager to import the certs to the computer and IIS, I've used Get-PfxCertificate and New-SPTrustedRootAuthority to get the cert into SharePoint's Manage Trust list. When I run Register-SPWorkflowService I get the error. More than once.
Here's my PowerShell command (server names scrubbed):
Register-SPWWorkflowService -SPSite "https://xxxxxxx.yyyyyyy.zzz" -WorkflowHostURI "https://aaaaaaa.yyyyyyy.zzz:12290"
I'm confused, and certainly no cert host. When I look at certlm, the auto generated cert shows up in the Trusted Root Certification Authorities. Doesn't that mean that it is registered as a trusted root authority? Central Admin, Security, Manage Trust shows the certificate in the list and it looks fine. I've not tried adding it from there using the New button (just the PowerShell), would that make a difference?
Or, am I headed down a rabbit trail and should be looking somewhere else? Or, should I scrap this, beg our network folks for a "real" cert and redo the whole thing? Or, what????
Thanks,
Steven