active-directory-javascript-nodejs-webapi-v2 | small Node.js Web API | Azure library

by Azure-Samples PowerShell Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | active-directory-javascript-nodejs-webapi-v2 Summary

active-directory-javascript-nodejs-webapi-v2 is a PowerShell library typically used in Cloud, Azure, Nodejs applications. active-directory-javascript-nodejs-webapi-v2 has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This sample demonstrates how to protect a Node.js Web API with the Microsoft identity platform and Azure Active Directory (Azure AD) using the passport-azure-ad library. You will need a client application for calling the web API. For a web API sample that is coupled with a client app, see: JavaScript Single-page application & Node.js web API Tutorial.

Support

Quality

Security

License

Reuse

Support

active-directory-javascript-nodejs-webapi-v2 has a low active ecosystem.

It has 55 star(s) with 32 fork(s). There are 48 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 10 have been closed. On average issues are closed in 137 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of active-directory-javascript-nodejs-webapi-v2 is current.

Quality

active-directory-javascript-nodejs-webapi-v2 has 0 bugs and 0 code smells.

Security

active-directory-javascript-nodejs-webapi-v2 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

active-directory-javascript-nodejs-webapi-v2 code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

active-directory-javascript-nodejs-webapi-v2 is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

active-directory-javascript-nodejs-webapi-v2 releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of active-directory-javascript-nodejs-webapi-v2

Get all kandi verified functions for this library.

active-directory-javascript-nodejs-webapi-v2 Key Features

No Key Features are available at this moment for active-directory-javascript-nodejs-webapi-v2.

active-directory-javascript-nodejs-webapi-v2 Examples and Code Snippets

No Code Snippets are available at this moment for active-directory-javascript-nodejs-webapi-v2.

Community Discussions

Trending Discussions on active-directory-javascript-nodejs-webapi-v2

Securing REST API Calls in SPAs using MSAL.js with Azure Active Directory - How to Pass Authentication Token to Bearer Strategy

Passport Azure AD This expression is not callable

"authentication failed due to: jwt audience is invalid" with Azure AD

QUESTION

Securing REST API Calls in SPAs using MSAL.js with Azure Active Directory - How to Pass Authentication Token to Bearer Strategy

Asked 2021-Jun-02 at 16:41

I am creating a SPA using React and Express. I am trying to include authentication using MSAL.js and have looked at Microsoft's tutorials for SPA. I've been able to implement this with React using @msal-react. While this does perform authentication, it does not protect the REST API from access by unauthenticated users.

I found the Active Directory Javascript Nodejs Web API that seems to provide a means for protecting the REST API using Passport and the Bearer strategy, but the links showing how to couple this with the client-side seem to be broken.

I'm not sure how to connect the authentication that is occurring on the client side with REST API. As I understand it, the authentication token has to be passed, but I am not sure how to pass that.

The server-side sample code has:

...

ANSWER

Answered 2021-Jun-02 at 16:41

When calling your protected REST API, you need to present an access token obtained by the client application (on behalf of the signed-in user). So the ID token won't do here -it's only meant for your client application as a proof of successful user authentication. (ideally, your client and service apps should be separate, each represented by an Azure AD app registration).

After authentication, you need to obtain an access token, by using one of the acquireToken* methods. You pass a token request object to that method. Here you need to specify what resources and permissions you are requesting an access token for. The access token that would work with calling your REST API shouldn't/won't work with other APIs.

The tutorial article you linked points to a sample using implicit flow. I would recommend using the more secure auth code flow.

This tutorial should cover your need. Check this section in particular.

p.s. for a React client app, see this.

Source https://stackoverflow.com/questions/65971268

QUESTION

Passport Azure AD This expression is not callable

Asked 2020-Jul-27 at 10:04

In the example the following piece of code is used:

...

ANSWER

Answered 2020-Jul-27 at 10:04

You can add types to each of the parameters.

new BearerStrategy(config, (token: ITokenPayload, done: CallableFunction) => ...

Source https://stackoverflow.com/questions/63111105

QUESTION

"authentication failed due to: jwt audience is invalid" with Azure AD

Asked 2020-Apr-11 at 22:59

First I'm describing how I setup my applications then I will describe how I'm using the APIs.

Setup

In my Azure Active Directory, I have two applications registered: UI and Backend
UI has the client ID clientId1 and backend has client ID clientId2 (it's a GUID, but for simplicity)
Both are under the same tenant tentant1 (single tenant)

Backend (Web API)

Backend has an exposed API with scope "api://clientId2/access_as_user" and authorized client "clientId1" with the scope just mentioned selected
I'm using passport and passport-azure-ad (I pretty much copied https://github.com/Azure-Samples/active-directory-javascript-nodejs-webapi-v2).
My config:
...

ANSWER

Answered 2020-Apr-11 at 22:59

Turns out their code in the repository is not using proper configuration to verify the scope access...

https://github.com/Azure-Samples/active-directory-javascript-nodejs-webapi-v2/blob/master/index.js#L41

Source https://stackoverflow.com/questions/61157721

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install active-directory-javascript-nodejs-webapi-v2

You can download it from GitHub.

Support

Use Stack Overflow to get support from the community. Ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before. Make sure that your questions or comments are tagged with [azure-active-directory azure-ad-b2c ms-identity adal msal]. If you find a bug in the sample, please raise the issue on GitHub Issues. To provide a recommendation, visit the following User Voice page.

Find more information at: