Book Image

Mobile Development with .NET - Second Edition

By : Can Bilgin
Book Image

Mobile Development with .NET - Second Edition

By: Can Bilgin

Overview of this book

Are you a .NET developer who wishes to develop mobile solutions without delving into the complexities of a mobile development platform? If so, this book is a perfect solution to help you build professional mobile apps without leaving the .NET ecosystem. Mobile Development with .NET will show you how to design, architect, and develop robust mobile applications for multiple platforms, including iOS, Android, and UWP using Xamarin, .NET Core, and Azure. With the help of real-world scenarios, you'll explore different phases of application development using Xamarin, from environment setup, design, and architecture to publishing. Throughout the book, you'll learn how to develop mobile apps using Xamarin and .NET Standard. You'll even be able to implement a web-based backend composed of microservices with .NET Core using various Azure services including, but not limited to, Azure Active Directory, Azure Functions. As you advance, you'll create data stores using popular database technologies such as Cosmos DB and data models such as the relational model and NoSQL. By the end of this mobile application development book, you'll be able to create cross-platform mobile applications that can be deployed as cloud-based PaaS and SaaS.
Table of Contents (25 chapters)
1
Section 1: Understanding .NET
5
Section 2: Xamarin and Xamarin.Forms
9
Section 3: Azure Cloud Services
14
Section 4: Advanced Mobile Development
18
Section 5: Application Life Cycle Management

Securing the application

In a microservice setup with a client-specific backend, multiple authentication strategies can be used to secure web applications. ASP.NET Core provides the required OWIN middleware components to support most of these scenarios.

Depending on the gateway and downstream services architecture, authentication/authorization can be implemented on the gateway and the user identity can be carried over to the backend services:

Figure 9.13 – Gateway Identity

Another approach would be where each service can utilize the same identity provider in a federated setup. In this setup, a dedicated Security Token Service (STS) would be used by client applications, and a trust relationship would need to be established between the STS and the app services:

Figure 9.14 – Microservice Identity

While choosing the authentication and authorization strategy, it is important to keep in mind that the identity consumer in...