Скачать или смотреть How to Prevent Orchestration Steps During Silent Token Acquisition in Azure AD B2C

Discover a practical solution for handling orchestration steps in Azure AD B2C to avoid unnecessary service calls during silent token acquisitions.
---
This video is based on the question https://stackoverflow.com/q/63146164/ asked by the user 'Ceros' ( https://stackoverflow.com/u/4533695/ ) and on the answer https://stackoverflow.com/a/63174756/ provided by the user 'Jas Suri - MSFT' ( https://stackoverflow.com/u/8357357/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Prevent Orchestration step from being executed in silent token acquisition

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

In the world of microservices and identity management, ensuring that services are not overwhelmed with unnecessary requests is crucial. A common issue faced by developers using Azure AD B2C is managing orchestration steps during silent token acquisitions. Specifically, you may have a situation where certain API interactions are triggered every time a user either signs in or creates an account. However, if a silent token request occurs, those actions can lead to spammy behavior, affecting service performance.

In this guide, we'll explore how to effectively manage these orchestration steps in order to prevent unwanted execution during silent token acquisitions.

The Problem Explained

When you set up your SignUp SignIn policy in Azure AD B2C, you have the option to call a RESTful API during specific orchestration steps in the user journey:

Orchestration Step: An individual action in the sequence that determines how a user's data is handled.

Silent Token Acquisition: A process where applications request an access token without user interaction, to access services on behalf of the user.

The challenge arises when the orchestration step that pushes information to the API is executed even during silent token requests. This can lead to repetitive calls when a token is being silently acquired, overloading your service unnecessarily.

Understanding <IncludeInSso>

As you navigate the orchestration steps, you may come across the <IncludeInSso> element. This setting determines whether the particular technical profile should be included in Single Sign-On (SSO) flows:

<IncludeInSso>:

If set to true, the orchestration step is executed during SSO, meaning it could trigger on silent requests.

If set to false, the orchestration step is excluded from SSO calls, which is what you typically want if trying to avoid unnecessary API spam.

The Solution

To resolve the issue of unwanted orchestration execution during silent token acquisition, follow these organized steps:

Step 1: Ignore <IncludeInSso>

Instead of focusing on modifying the <IncludeInSso> attribute, the pattern to adopt here is to implement session management.

Step 2: Implement Session Management

You can achieve this by adding a session management technical profile to your REST API technical profile. Below is a sample XML snippet to demonstrate this approach:

[[See Video to Reveal this Text or Code Snippet]]

This line ensures that the calls to your API are managed correctly and won't be made during silent token acquisition. By referring to a session management profile, it provides the necessary control over how and when the orchestration step gets executed, effectively circumventing the issues associated with silent requests.

Conclusion

Managing orchestration steps in Azure AD B2C during silent token acquisition can be complicated, but by effectively implementing session management and configuring your technical profiles, you can prevent unwanted service requests and keep your application running smoothly. Safeguarding your services from spammy behavior is essential to enhancing performance and user experience.

By following the steps outlined above, you can create a more efficient user journey without unnecessary interruptions in your service architecture. Happy coding!