Wanted to record brief demo of how to protect WebAPI data endpoint with ADAL (Azure Active Directory) Authentication Library. Azure Portal enables us to register custom SPA (Single Page Application) for secure API calls to backend REST data sources. OAuth Bearer HTTP headers are applied to provide security with JWT tokens (JSON Web Token). Video shows all steps from Azure Portal registration to F12 validation of REST data calls.
The video below demo shows how to create a new SPFx SharePoint Framework web part including Gulp, Visual Studio code, project folder tour, and TypeScript import references.
Great way to start developing for Modern pages (SharePoint Online and SharePoint 2016) running localhost on a developer workstation. No need for a SharePoint virtual machine. Cheers!
SharePoint is often treated as a final SAAS product to perform Microsoft native functions only. Management can be reluctant to engage customization and development for the perceived cost.
However, what is the cost of lacking a needed business tool? Lost productivity and opportunity?
What is the cost to create native SP features? Make a blank IIS website? Then create your own search, audit, permission interface, file store, REST endpoint, etc.?
Today is the best time ever to be a developer. Many services and many tools. Agile design can be applied to leverage 90% native platform with 10% custom code to spin up helpful business applications with low cost. Micro services, REST api, and JavaScript frameworks provide the building blocks. Developers are challenged to learn these new tools. Ones that do can help deliver business value faster than ever.
Remember, SharePoint is a service– not the final product.
Features
Authentication – User context. Password management, new account creation, integrated single sign-on.
I needed a quick reference to introduce developers with the SharePoint 2013 App Model.
For traditional ASP.Net and Dot Net coders there is a wide philosophy gap to cross when considering new applications written mostly in front-end JavaScript, HTML, and CSS. Instead of coding “in” SharePoint (to augment the core product) we now code “next to” SharePoint (with additive REST/JSON endpoints).
The stability which comes from this approach is significant. We wan to run on-premise SharePoint similar to how Microsoft operates Office 365. No more SharePoint customization lost during patching. No more late night WSP and IISRESET outages. Code can be modified more fluidly and IE breakpoints can even be set at a single user’s desktop when troubleshooting. Exciting and powerful tools – which require a new way of thinking.
Please fee free to download the poster I made below. Hope you find it helpful!
