Skip to content

Commit 320d452

Browse files
Merge pull request #293749 from Akhilesh-microsoft/ACA/authentication_GH_286823
[GH_286823]: Analyzed and fixed the documentation issue; reviewed and fixed the issues w.r.t freshness. Updated ms.date
2 parents 9541d3a + 02c4f59 commit 320d452

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/container-apps/authentication.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: conceptual
8-
ms.date: 04/20/2022
8+
ms.date: 01/30/2025
99
ms.author: cshoe
1010
---
1111

@@ -105,7 +105,7 @@ In the [Azure portal](https://portal.azure.com), you can edit your container app
105105
With this option, you don't need to write any authentication code in your app. Finer authorization, such as role-specific authorization, can be handled by inspecting the user's claims (see [Access user claims](#access-user-claims-in-application-code)).
106106

107107
> [!CAUTION]
108-
> Restricting access in this way applies to all calls to your app, which may not be desirable for apps wanting a publicly available home page, as in many single-page applications.
108+
> Restricting access to your application applies to all requests to your app. These restrictions may not be preferable for apps with a publicly available web page, as is typical in many single-page applications.
109109
110110
> [!NOTE]
111111
> By default, any user in your Microsoft Entra tenant can request a token for your application from Microsoft Entra ID. You can [configure the application in Microsoft Entra ID](../active-directory/develop/howto-restrict-your-app-to-a-set-of-users.md) if you want to restrict access to your app to a defined set of users.
@@ -133,6 +133,9 @@ In the sign-in page, or the navigation bar, or any other location of your app, a
133133

134134
When the user selects on one of the links, the UI for the respective providers is displayed to the user.
135135

136+
> [!WARNING]
137+
> For client-side apps, the client's route manager may intercept the `/.auth/login/` routes, preventing the auth side-car from receiving requests. Ensure your client-side routing configuration allows the server to process these routes.
138+
136139
To redirect the user post-sign-in to a custom URL, use the `post_login_redirect_uri` query string parameter (not to be confused with the Redirect URI in your identity provider configuration). For example, to navigate the user to `/Home/Index` after sign-in, use the following HTML code:
137140

138141
```html
@@ -215,7 +218,7 @@ For all language frameworks, Container Apps makes the claims in the incoming tok
215218
Code that is written in any language or framework can get the information that it needs from these headers.
216219

217220
> [!NOTE]
218-
> Different language frameworks may present these headers to the app code in different formats, such as lowercase or title case.
221+
> Different language frameworks might present these headers to the app code in different formats, such as lowercase or title case.
219222
220223
## Next steps
221224

0 commit comments

Comments
 (0)