The Tailspin scenario

Sample code

Tailspin is a fictional company that is developing a SaaS application named Surveys. This application enables organizations to create and publish online surveys.

• An organization can sign up for the application.
• After the organization is signed up, users can sign into the application with their organizational credentials.
• Users can create, edit, and publish surveys.

Users can create, edit, and view surveys

Authenticated users can view surveys that they created or have contributor rights to. They can create new surveys. Notice that the user is signed in with an organizational identity, bob@contoso.com.

This screenshot shows the Edit Survey page:

Users can also view any surveys created by other users within the same tenant.

Survey owners can invite contributors

When a user creates a survey, he or she can invite other people to be contributors on the survey. Contributors can edit the survey, but can't delete or publish it.

A user can add contributors from other tenants. Adding contributors enables cross-tenant sharing of resources. In this screenshot, Bob (bob@contoso.com) is adding Alice (alice@fabrikam.com) as a contributor to a survey that Bob created.

When Alice logs in, she sees the survey listed under "Surveys I can contribute to".

Alice signs into her own tenant, not as a guest of the Contoso tenant. Alice has contributor permissions only for that survey. She can't view other surveys from the Contoso tenant.

Architecture

The Surveys application consists of a web front end and a web API backend. Both are implemented using ASP.NET Core.

The web application uses Azure Active Directory (Azure AD) to authenticate users. The web application also calls Azure AD to get OAuth 2 access tokens for the Web API. Access tokens are cached in Azure Cache for Redis. The cache enables multiple instances to share the same token cache (for example, in a server farm).

Next