| services | platforms | author |
|---|---|---|
active-directory |
nodejs |
brandwe |
This Node.js app will give you with a quick and easy way to set up a Web application in node.js with Express using OpenID Connect. The sample server included in the download is designed to run on any platform.
We've released all of the source code for this example in GitHub under an MIT license, so feel free to clone (or even better, fork!) and provide feedback on the forums.
Getting started with the sample is easy. It is configured to run out of the box with minimal setup.
To use this sample you will need a Azure Active Directory Tenant. If you're not sure what a tenant is or how you would get one, read What is an Azure AD tenant? or Sign up for Azure as an organization. These docs should get you started on your way to using Azure AD.
To successfully use this sample, you need a working installation of Node.js.
Next, clone the sample repo and install the project's NPM dependencies.
From your shell or command line:
$ git clone git@github.com:Azure-Samples/active-directory-node-webapp-openidconnect.git$ cd active-directory-node-webapp-openidconnect$ npm install
Provided for simplicity, config.js contains some simple variables. In a
real application, it would be best to use environment variables, a Node.js
configuration system, or Azure Key Vault
to store credentials securely, outside of your source control system.
In config.js, your tenant ID should go in the realm configuration field.
NOTE: You may also pass the issuer: value if you wish to validate that as well.
$ node app.js
Is the server output hard to understand?: We use bunyan for logging in this sample. The console won't make much sense to you unless you also install bunyan and run the server like above but pipe it through the bunyan binary:
$ npm install -g bunyan$ node app.js | bunyan
You will have a server successfully running on http://localhost:3000.
We would like to acknowledge the folks who own/contribute to the following projects for their support of Azure Active Directory and their libraries that were used to build this sample. In places where we forked these libraries to add additional functionality, we ensured that the chain of forking remains intact so you can navigate back to the original package. Working with such great partners in the open source community clearly illustrates what open collaboration can accomplish. Thank you!
Coming soon...