-
Notifications
You must be signed in to change notification settings - Fork 219
Web API Template
Jean-Marc Prieur edited this page May 5, 2020
·
33 revisions
The following animated image shows how you can build the NuGet package containing the project templates for .NET Core, install them locally, and create a new Web API. It also shows the important part of the code. You can open the image in a new tab if you want to get a full resolution image.
cd ProjectTemplates
msbuild /t:restore
msbuild /t:pack
cd bin
cd Debug
dotnet new -i Microsoft.Identity.Web.ProjectTemplates.0.1.0.nupkg
Microsoft identity platform Web API
mkdir webapi
cd webapi
dotnet new webapi2 --auth SingleOrg
msbuild
cd ..
AzureAD B2C B2C
mkdir webapi-b2c
cd webapi-b2c
dotnet new webapi2 --auth IndividualB2C
msbuild
cd ..
cd ProjectTemplates
dotnet new -u Microsoft.Identity.Web.ProjectTemplates
- Home
- Why use Microsoft Identity Web?
- Web apps
- Web APIs
- Using certificates
- Minimal support for .NET FW Classic
- Logging
- Azure AD B2C limitations
- Samples
- Web apps
- Web app samples
- Web app template
- Call an API from a web app
- Managing incremental consent and conditional access
- Web app troubleshooting
- Deploy to App Services Linux containers or with proxies
- SameSite cookies
- Hybrid SPA
- Web APIs
- Web API samples
- Web API template
- Call an API from a web API
- Token Decryption
- Web API troubleshooting
- web API protected by ACLs instead of app roles
- gRPC apps
- Azure Functions
- Long running processes in web APIs
- Authorization policies
- Generic API
- Customization
- Logging
- Calling graph with specific scopes/tenant
- Multiple Authentication Schemes
- Utility classes
- Setting FIC+MSI
- Mixing web app and web API
- Deploying to Azure App Services
- Azure AD B2C issuer claim support
- Performance
- specify Microsoft Graph scopes and app-permissions
- Integrate with Azure App Services authentication
- Ajax calls and incremental consent and conditional access
- Back channel proxys
- Client capabilities