Programmatic access to Custom Policies and Keysets
[!NOTE] Custom Policies programmatic access is in public preview
[!NOTE] Keysets programmatic access is in private preview. To get access for trying out this feature, please send a email to firstname.lastname@example.org with your tenant name that you want enabled.
This is a sample command line tool that demonstrates managing custom trust framework policies (custom policy for short) and Policy keys in an Azure AD B2C tenant. Custom policy allows you to customize every aspect of the authentication flow. Azure AD B2C uses Policy keys to manage your secrets.
This project framework provides the following features:
- Create, Read, Update and Delete of TrustFramework Policies
- Create, Read, Update and Delete of KeySets
- Upload Secret, Certificate and Pkcs12 of Keysets
- Get Backed up Keysets
- Generate Key of Keysets
- Get Active Key in a Keyset
This sample requires the following:
NOTE: This API only accepts user tokens, and not application tokens. See more information below about Delegated Permissions.
Create global administrator
- An global administrator account is required to run admin-level operations and to consent to application permissions. (for example: email@example.com)
Register the delegated permissions application
- Sign in to the Application Registration Portal using your Microsoft account.
- Select Add an app, and enter a friendly name for the application (such as Console App for Microsoft Graph (Delegated perms)). Click Create.
- On the application registration page, select Add Platform. Select the Native App tile and save your change. The delegated permissions operations in this sample use permissions that are specified in the AuthenticationHelper.cs file. This is why you don't need to assign any permissions to the app on this page.
- Open the project PolicyAndKeys-Client and then update App.Config file in Visual Studio with the following.
- Make the Application Id value for this app the value of the ida:ClientId string.
- Update ida:Tenant with the name of your tenant. (for example: myb2ctenantname.onmicrosoft.com)
Build and run the sample
- Open the sample solution in Visual Studio.
- There are 2 projects - PolicyAndKeys-Client and PolicyAndKeys-Lib.
- In the PolicyAndKeys-Client project, Make sure to Replace the tenant name and ClientId in app.config by following Register the delegated permissions application
- Build the sample.
- Using cmd or PowerShell, navigate to
/bin/Debug. Run the client executable PolicyAndKeys-Client.exe.
- Sign in as a global administrator. (for example: firstname.lastname@example.org)
- The output will show the results of calling the Graph API for trustFrameworkPolices.
Questions and comments
Questions about this sample should be posted to Stack Overflow. Make sure that your questions or comments are tagged with [azure-ad-b2c].
If you'd like to contribute to this sample, see CONTRIBUTING.MD.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact email@example.com with any additional questions or comments.## Resources
The sample uses the Microsoft Authentication Library (MSAL) for authentication. The sample demonstrates both delegated admin permissions. (app only permissions are not supported yet)
Delegated permissions are used by apps that have a signed-in user present (in this case tenant administrator). For these apps either the user or an administrator consents to the permissions that the app requests and the app is delegated permission to act as the signed-in user when making calls to Microsoft Graph. Some delegated permissions can be consented to by non-administrative users, but some higher-privileged permissions require administrator consent.
See Delegated permissions, Application permissions, and effective permissions for more information about these permission types.