Below is a sample file to use with Visio Web Part for testing SharePoint Server. Hope that helps. Cheers!
Below is a example of how to wrap System.DirectoryServices.AccountManagement.PrincipalContext.ValidateCredentials() with REST api container for electronic signature over REST api call. This enables web based forms to be “signed” for business purpose with given user’s password. The api will return “true” if given a valid Domain, User, and Password. However, should any invalid input be given or an exception occur it merely responds “false.”
NOTE – This API should ONLY be used over HTTPS for secure encrypted transport. Demo video shows HTTP for educational purposes only.
// Verify Active Directory username and password
bool isValid = false;
// create a "principal context" - e.g. your domain (could be machine, too)
using (PrincipalContext pc = new PrincipalContext(ContextType.Domain, settings.Domain))
// validate the credentials
isValid = pc.ValidateCredentials(settings.User, settings.Password);
// Data Class for Settings
public class verifySettings
public string Domain;
public string User;
public string Password;
Here we have a simple AngularJS 1x to-do list saving JSON payload data to a SharePoint Online list hosted in Office 365. Authentication is achieved with EditThisCookie and ModHeader chrome extensions. By exporting cookies from a valid Office 365 session to the “chromecors” session we are authenticated and enable to execute REST apis. ModHeader is used for “Origin : tenant.sharepoint.com” to provide source detail.
NOTE – PDF format updated to include both SharePoint 2013 and 2016 notes.
Ever wondered what fixes are inside of a given CU? Please see attached PDF with full detail. I wanted a new format for easy reading. Show management and make the business case for why downtime should be taken to apply CUs. Also posted at http://sharepointupdates.com/
If you found this helpful, please leave a comment.
|What’s in that patch – Sep 2018.PDF|