This sample default application is Contoso BadgeMeUp. It is easy to run the application locally to explore how it works within the context of the other SaaS modules.
Contoso BadgeMeUp is a simple SaaS application that Contoso sells to companies that want a great tool to improve the culture within their organization.
This project hosts an application for providing the intended SaaS functions to valid Tenants.
For a design overview, please see the SaaS.Application.Web page in our documentation site.
The application has been developed using Razor pages with code behind. Automatic reference to the project name has been established through the string resource class (SR.cs) for the scoped CSS reference in _Layout.cshtml. See the Pages and Service directories for relevant display or service logic.
Throughout the project, various "TODO (SaaS)" tags have been added. They are placed around identifiers you will want to alter to suit your individual application if you plan to build off of the template. Either navigate using the todo list in Visual Studio or search for "TODO (SaaS)" to quickly address these areas and find points to begin development.
Authentication has been implemented utilizing Azure AD B2C and utilizing the same underlying claims as the Signup application. Further, a demonstration of tenant-specific app logic has been implemented as a starting guide to work by. When an authenticated user is signed into the application, you may visit the route path from the site base to fetch public information regarding the tenant and have it displayed. For instance, when you register the route "MySoftwareCompany" during signup and run the app locally, this will look like:
Within this folder you will find two subfolders:
- Saas.Application.Web - the C# project for the web app.
- deployment - a set of tools for deploying the web app for production
- The sub-subfolder act is for deploying the web app for remote debugging
The service depends on:
- The Identity Foundation that was deployed a spart of the Identity Foundation and on the Microsoft Graph API.
- The SaaS Permissions Services API.
- The SaaS Administration Service API.
To work with the SaaS Application Web app it must first be provisions to your Azure ASDK resource group. This is true even if you initially is planning to run the web app in your local development environment.
The provisioning ensure that configuration and settings to be correctly added to your Azure App Configuration store and readies the API for later deployment to Azure.
Provisioning is easy:
-
Navigate to the sub folder
deployment. -
Run these commands:
./setup.sh ./run.sh
Now you're ready to move on.
Guidelines for getting up and running with SaaS Signup Administration in your local development, are identical to the guidelines found the Requirements and the Configuration, settings and secrets when running locally section in the SaaS Permissions Service readme.
--- TODO BEGIN ---
Needs more investigation.
Add some guidelines about how to do this. Probably by leveraging ngrok...
---TODO END ---
The guidelines are identity to How to Deploy SaaS Permissions Service API to Azure.
The guidelines are identity to Debugging in Azure for the SaaS Permissions Service API
You'll need to configure your B2C instance for an external authentication provider. Additional documentation is available here.