Could not load type ‘System.IdentityModel.Tokens.TokenValidationParameters’ from assembly ‘System.IdentityModel.Tokens.Jwt, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
( others at IdentityServer3#3017 saw the same with JWT breaking change)
Recently I came across a condition where Workflow 2013 instance were not running. Root cause was a missing outbound certificate. Below are screenshots and PowerShell steps to resolve. No Windows service restart, reboot, or IISRESET was needed. Just apply config and test again. Cheers!
1) Verify outbound certificate missing. Expect $oc to be null.
# Expect to be NULL (MISSING)
2) Locate thumbprint of certificate with most forward expiration
Set-WFNextOutboundCertificateReference-ServiceUri$wf.Endpoints-Thumbprint[ADD REAL CERT THUMBPRINT HERE]
# Expect to be NOT NULL (SHOW THUMBPRINT)
4) Test by running Workflow 2013. Open web browser and click WF2013 test to run again. Verify completed without errors. Bonus points if the workflow has an email step and you receive the email OK.
EventID 563: Private key certificate with thumbprint ‘F4545D83AE81EBA21996B139BB44E614145F9057’ could not be found in the local machine certificate store. This may cause failures for running workflows which depend on this certificate.
Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.InvalidOperationexception: No valid outbound signing keys were found. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute (ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.Execute.ActivityWorkItem.ExecuteBody (ActivityExecutor exectore, BookmarkManager bookManager, Location resultLocation)
Recently I wanted to create a Communication site in Office 365 but did not see the “+New” menu on the tenant SharePoint landing page. However, I switched to another tenant and watched HTTP traffic over F12 Network tools. Here I could see the exact URL for the APSX new Communication Site form.
Adding the URL suffix “/_layouts/15/CreateGroup.aspx” allowed me to successfully create a Communication Site on other tenants. Hope this helps! Cheers.