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

by Azure-Samples JavaScript Version: 83083 License: MIT

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

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

active-directory-b2c-javascript-nodejs-webapi is a JavaScript library typically used in Cloud, Azure applications. active-directory-b2c-javascript-nodejs-webapi 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 Microsoft identity platform and Azure AD B2C using the passport-azure-ad library.

Support

Quality

Security

License

Reuse

Support

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

It has 96 star(s) with 56 fork(s). There are 50 watchers for this library.

It had no major release in the last 12 months.

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

It has a neutral sentiment in the developer community.

The latest version of active-directory-b2c-javascript-nodejs-webapi is 83083

Quality

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

Security

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

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

There are 0 security hotspots that need review.

License

active-directory-b2c-javascript-nodejs-webapi 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-b2c-javascript-nodejs-webapi releases are available to install and integrate.

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-b2c-javascript-nodejs-webapi

Get all kandi verified functions for this library.

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

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

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

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

Community Discussions

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

Can I serve a directory with express without bypassing authentication?

Google Access Token With msal loginPopup?

API won't authenticate against AAD with token passed from SPA using MSAL

QUESTION

Can I serve a directory with express without bypassing authentication?

Asked 2020-Dec-03 at 22:21

I have a bunch of legacy html files I would like to serve to authenticated users. The authentication provider is Azure AD B2C and I found this Nodejs template that authenticates users with AD B2C.

I can serve single html files and authenticate them with something like this.

...

ANSWER

Answered 2020-Dec-03 at 22:21

Try something like this:

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

QUESTION

Google Access Token With msal loginPopup?

Asked 2020-Sep-08 at 10:00

I'm trying to use Azure Active Directory B2C for my authentication flow for an SPA with a Node JS API. I'm using the code samples provided in the official tutorials (https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp and https://github.com/Azure-Samples/active-directory-b2c-javascript-nodejs-webapi). I've set up everything correctly as far as I know, and I've created Facebook and Google IDP registrations according to the documentation provided. I've set up the b2cPolicies using the default SignUpSignIn User Flow, so there's really nothing to configure there except to specify that I'm using email, Google and Facebook. I'm able to authenticate into Azure's sample SPA with both Google and Facebook without issue, the id_tokens are fine. When I click the button to access the /hello endpoint from the sample API, only the email and Facebook flows produce the correct access_token from the myMSALObj.aquireTokenSilent call, however, when using Google, the "Choose an Account" popup appears a second time. When I'm only logged into a single account, it appears briefly and vanishes again, but when logged into multiple accounts, I have to select one again. This is kind of a terrible user experience, is there some way around this?

...

ANSWER

Answered 2020-Sep-08 at 10:00

In the acquireTokenSilent() call, pass in a parameter within the MSAL config object: login_hint=emailaddress. Then use Custom Policy to pass this value back to the Google IdP, such that Google skips its account selection page.

You can do that by adding an input claim to the Google technical profile:

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

QUESTION

API won't authenticate against AAD with token passed from SPA using MSAL

Asked 2018-Jul-13 at 13:02

I'm trying to adapt the sample B2C code referenced here and here to work against our organizations AAD.

I have a SPA app that is successfully authenticating with AAD via MSAL and receiving a token. The SPA app can use the token to pull data from the MS Graph API -- so I'm certain the token is valid.

The SPA is currently running locally @ localhost:9000.

I have a second app that is a Nodejs API running @ localhost:3000. The SPA app makes a call to the API passing the same token used for the GraphAPI. The API app is supposed to use that token to authenticate the user and provide access to the API; however, I only ever get back a 401 - Unauthorized.

(I'm using Aurelia for my client side code. HTTP request is made using Aurelia's HTTP client).

Here is the SPA code used to call the API:

...

ANSWER

Answered 2017-Jul-24 at 17:46

Tokens are like bank checks: they can only be cached by the person they were written for. A token issued for the MS Graph will have as audience the Microsoft Graph, and should be accepted by the Microsoft Graph only. Any other API X receiving that token should refuse it. A client intending to invoke X should request a token for X, regardless of whether it already has a token for another service (like the Microsoft graph). Here there's an example of that flow, implemented with ADAL JS: https://azure.microsoft.com/en-us/resources/samples/active-directory-angularjs-singlepageapp-dotnet-webapi/ At this point Azure AD v2 (used by MSAL) is not capable of issues access tokens for custom API: the feature is being worked on, but we have no ETA for when it will become available in production. Until then, this topology isn't supported with v2 (hence MSAL JS). Sorry!

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

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

Vulnerabilities

No vulnerabilities reported

Install active-directory-b2c-javascript-nodejs-webapi

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: