You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/develop/authentication-scenarios.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,7 +167,7 @@ This attribute causes ASP.NET to check for the presence of a session cookie cont
167
167
User authentication happens via the browser. The OpenID protocol uses standard HTTP protocol messages.
168
168
* The web app sends an HTTP 302 (redirect) to the browser to use Azure AD.
169
169
* When the user is authenticated, Azure AD sends the token to the web app by using a redirect through the browser.
170
-
* The redirect is provided by the web app in the form of a redirect URI. This redirect URI is registered with the Azure AD application object. There can be several redirect URIs because the application may be deployed at several URLs. So the web app will also need to specify the redirect URi to use.
170
+
* The redirect is provided by the web app in the form of a redirect URI. This redirect URI is registered with the Azure AD application object. There can be several redirect URIs because the application may be deployed at several URLs. So the web app will also need to specify the redirect URI to use.
171
171
* Azure AD verifies that the redirect URI sent by the web app is one of the registered redirect URIs for the app.
172
172
173
173
## Desktop and mobile app sign-in flow with Azure AD
0 commit comments