SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

Blog

VIDEO – Azure AD protected Web API in an AngularJS SPA

Recently I walked through an Azure AD Web API sample project on GitHub at https://github.com/Azure-Samples/active-directory-angularjs-singlepageapp-dotnet-webapi and recorded a brief 14 minute video of the install and deployment steps.   Watch below and enjoy.  Cheers! 

shades_smile

Video

Screenshots

image
image

image
image

Error Message

Could not load type ‘System.IdentityModel.Tokens.TokenValidationParameters’ from assembly ‘System.IdentityModel.Tokens.Jwt, Version=5.0.0.127, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
( others at IdentityServer3#3017 saw the same with JWT breaking change)

Extra NuGet Package Step

References

FIXED – Workflow 2013 Suspended (Event ID 563) – No valid outbound signing keys were found

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!

shades_smile

Resolution Steps

1) Verify outbound certificate missing.  Expect $oc to be null.

2) Locate thumbprint of certificate with most forward expiration

3) Apply thumbprint and certificate

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.

Errors

  • 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)

Screenshots

clip_image001
clip_image001[6]
image
clip_image001[8]
image
image

References

Create Communication Site – URL Trick

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. 

shades_smile

Resolution

  1. Navigate to portal root https://tenant.sharepoint.com/
  2. Append URL with suffix “/_layouts/15/CreateGroup.aspx” for a complete URL such as https://tenant.sharepoint.com/_layouts/15/CreateGroup.aspx
  3. Form to create Team or Communication Site is now visible
  4. Select “Communication
  5. Provide URL, type, and description

Screenshots

1
2
3
4
5
6
7
8

PowerShell Error

err

New-PNPTenantSite : The web template SITEPAGEPUBLISHING#0 is not available for sites on this tenant.

Reference

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲