ms-identity-dotnetcore-b2c-account-management | NET Core console application using Microsoft Graph | Azure library

by Azure-Samples C# Version: 128042 License: MIT

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

kandi X-RAY | ms-identity-dotnetcore-b2c-account-management Summary

ms-identity-dotnetcore-b2c-account-management is a C# library typically used in Cloud, Azure applications. ms-identity-dotnetcore-b2c-account-management has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

page_type: sample languages: - csharp products: - azure-active-directory - azure-active-directory-b2c - dotnet - dotnet-core - ms-graph description: ".NET Core console application using Microsoft Graph for Azure AD B2C user account management." urlFragment: "manage-b2c-users-dotnet-core-ms-graph" ---.

Support

Quality

Security

License

Reuse

Support

ms-identity-dotnetcore-b2c-account-management has a low active ecosystem.

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

It had no major release in the last 12 months.

There are 3 open issues and 8 have been closed. On average issues are closed in 51 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of ms-identity-dotnetcore-b2c-account-management is 128042

Quality

ms-identity-dotnetcore-b2c-account-management has 0 bugs and 0 code smells.

Security

ms-identity-dotnetcore-b2c-account-management has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ms-identity-dotnetcore-b2c-account-management code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ms-identity-dotnetcore-b2c-account-management 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

ms-identity-dotnetcore-b2c-account-management releases are available to install and integrate.

Installation instructions, 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 ms-identity-dotnetcore-b2c-account-management

Get all kandi verified functions for this library.

ms-identity-dotnetcore-b2c-account-management Key Features

No Key Features are available at this moment for ms-identity-dotnetcore-b2c-account-management.

ms-identity-dotnetcore-b2c-account-management Examples and Code Snippets

No Code Snippets are available at this moment for ms-identity-dotnetcore-b2c-account-management.

Community Discussions

Trending Discussions on ms-identity-dotnetcore-b2c-account-management

Microsoft Graph access token refresh

Why do I encounter "Authorization_RequestDenied: Insufficient privileges to complete the operation" when resetting a password via Graph API

Azure's Graph api passwordprofile NULL for b2c users

QUESTION

Microsoft Graph access token refresh

Asked 2021-Dec-08 at 06:20

I am writing an application that uses the "OAuth 2.0 client credentials grant flow" to get an access token for calling the Microsoft Graph API. The application authenticates as itself, not on behalf of a signed in user.

I based my code off of this example from Microsoft.

This is how I initialize the GraphServiceClient:

...

ANSWER

Answered 2021-Dec-08 at 06:18

According to your code snippet above, I think you are using the graph SDK and using the client credential flow as the authentication.

So we are no need to generate access token here but just using the graphClient to call the graph api and gather the information you needed. And due to this mode, it won't appear the token expired situation as each time you call an api you will new clientSecretCredential before it.

And let's come back to the refresh, azure ad provide refresh token for refreshing the access token when it expired as refresh token has much longer expire time than access token, when we try to get the refresh token, we need to append offline_access to the scope when generate the access. But using client credential flow means your app requests a new token with it's own credentials, so it's no need to using refresh token to avoid making signed-in user sign in again. Using credential flow shouldn't return refresh token.

Then you may have some ideas that you insist on using refresh the expired token process, then what you only can do is generate an access token first and save the token with its expired time in some place, and using the access token as the http request header and calling graph api. Then the code should like this, but I don't think you're willing to using this kind of code, you may also refer to this document for more details:

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

QUESTION

Why do I encounter "Authorization_RequestDenied: Insufficient privileges to complete the operation" when resetting a password via Graph API

Asked 2020-Nov-06 at 09:36

I have cloned the MS Identity DotNetCore B2C Account Management code sample and configured it for my B2C tenant. The get user and delete user commands all work. However when I try to use command [5] Update user password I encounter this error:

...

ANSWER

Answered 2020-Jun-29 at 01:40

To update the passwordProfile of the user, the Directory.AccessAsUser.All permission is needed.

See the doc:

And you should note the Directory.AccessAsUser.All is the Delegated permission, not Application permission. It means the permission will not take effect in the client credential flow(the sample you provided uses it), so when you use the Microsoft Graph SDK, you could not use the Client credentials provider, your option is to use the Authorization code provider(recommended).

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

QUESTION

Azure's Graph api passwordprofile NULL for b2c users

Asked 2020-Mar-19 at 10:23

Users sign up/login via Azure AD B2C using Identity provider Local Account-Email.

I can see users signed up (with their password) for the tenant: When I run example "Manage User Accounts with Graph API" to check for local identity passwordProfiles they show null. My assumption is this property is automatically populated when a user creates the password same as other User resources.

Can someone give me some guidance what I'm missing?

...

ANSWER

Answered 2020-Mar-19 at 10:23

It is an expected result.

Azure AD B2C doesn't require the local identity users to change password next sign in. As the document says:

The property must set to .forceChangePasswordNextSignIn false.

Set forceChangePasswordNextSignIn as true is meaningless. In this case, passwordProfile won't be visible through GET method of Microsoft Graph API.

You can quickly verify it in Microsoft Graph Explorer.

For example, if you create a user with "forceChangePasswordNextSignIn": true in an Azure AD tenant, you will get passwordProfile in the result.

If you create a user with "forceChangePasswordNextSignIn": true in an Azure AD B2C tenant, you can get "passwordProfile" in the result but the password is null.

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

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

Vulnerabilities

No vulnerabilities reported

Install ms-identity-dotnetcore-b2c-account-management

Clone the repo or download and extract the [ZIP archive](https://github.com/Azure-Samples/ms-identity-dotnetcore-b2c-account-management/archive/master.zip).
Clone the repo or download and extract the [ZIP archive](https://github.com/Azure-Samples/ms-identity-dotnetcore-b2c-account-management/archive/master.zip)
Modify ./src/appsettings.json with values appropriate for your environment: Azure AD B2C tenant ID Registered application’s Application (client) ID Registered application’s Client secret
Build the application with dotnet build: ```console azureuser@machine:~/ms-identity-dotnetcore-b2c-account-management$ cd src azureuser@machine:~/ms-identity-dotnetcore-b2c-account-management/src$ dotnet build Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Core Copyright (C) Microsoft Corporation. All rights reserved. Restore completed in 431.62 ms for /home/azureuser/ms-identity-dotnetcore-b2c-account-management/src/b2c-ms-graph.csproj. b2c-ms-graph -> /home/azureuser/ms-identity-dotnetcore-b2c-account-management/src/bin/Debug/netcoreapp3.0/b2c-ms-graph.dll Build succeeded. 0 Warning(s) 0 Error(s) Time Elapsed 00:00:02.62 ``` 4. Add 2 custom attributes to your B2C instance in order to run all the sample operations with custom attributes involved. Attributes to add: - FavouriteSeason (string) - LovesPets (boolean)

Support

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com. When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. <!-- LINKS -→ [msal-doc]: https://docs.microsoft.com/azure/active-directory/develop/msal-overview [msal-pkg]: https://www.nuget.org/packages/Microsoft.Identity.Client/ [msal-ref]: https://docs.microsoft.com/dotnet/api/microsoft.identity.client?view=azure-dotnet [msal-src]: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet. [config-doc]: https://docs.microsoft.com/aspnet/core/fundamentals/configuration [config-pkg]: https://www.nuget.org/packages/Microsoft.Extensions.Configuration/ [config-ref]: https://docs.microsoft.com/dotnet/api/microsoft.extensions.configuration [config-src]: https://github.com/dotnet/extensions. [graph-doc]: https://docs.microsoft.com/graph/ [graph-auth-pkg]: https://www.nuget.org/packages/Microsoft.Graph.Auth/ [graph-beta-pkg]: https://www.nuget.org/packages/Microsoft.Graph.Beta/ [graph-auth-ref]: https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/dev/docs/overview.md <!--[graph-beta-ref]: USES graph-auth-ref -→ [graph-auth-src]: https://github.com/microsoftgraph/msgraph-sdk-dotnet [graph-beta-src]: https://github.com/microsoftgraph/msgraph-beta-sdk-dotnet. [ConfidentialClientApplication]: https://docs.microsoft.com/dotnet/api/microsoft.identity.client.iconfidentialclientapplication [ClientCredentialProvider]: https://github.com/microsoftgraph/msgraph-sdk-dotnet-auth#b-client-credential-provider [GraphServiceClient]: https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/dev/docs/overview.md#graphserviceclient.

Find more information at: