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
When applications are made up of multiple individual web application instances using different domain suffixes or different ports or paths in the URL, the individual web application instances must be published in separate Azure AD Application Proxy apps and the following problems might arise:
19
-
1. Pre-authentication- The client must separately acquire an access token or cookie for each Azure AD Application Proxy apps. This might lead to additional redirects to login.microsoftonline.com and CORS issues.
18
+
When applications are made up of multiple individual web application using different domain suffixes or different ports or paths in the URL, the individual web application instances must be published in separate Azure AD Application Proxy apps and the following problems might arise:
19
+
1. Pre-authentication- The client must separately acquire an access token or cookie for each Azure AD Application Proxy app. This might lead to additional redirects to login.microsoftonline.com and CORS issues.
20
20
2. CORS issues- Cross-origin resource sharing calls (OPTIONS request) might be triggered to validate if the caller web app is allowed to access the URL of the targeted web app. These will be blocked by the Azure AD Application Proxy Cloud service, since these requests cannot contain authentication information.
21
21
3. Poor app management- Multiple enterprise apps are created to enable access to a private app adding friction to the app management experience.
22
22
@@ -26,10 +26,10 @@ The following figure shows an example for complex application domain structure.
26
26
27
27
With [Azure AD Application Proxy](application-proxy.md), you can address this issue by using complex application publishing that is made up of multiple URLs across various domains.
28
28
29
-

A complex app has multiple app segments, with each app segment being a pair of an internal & external URL.
32
-
There is one conditional access policy associated with the app and access to any of the external URL's work with pre-authentication with the same set of policies enforced for all.
32
+
There is one conditional access policy associated with the app and access to any of the external URLs work with pre-authentication with the same set of policies that are enforced for all.
33
33
34
34
This solution that allows user to:
35
35
@@ -39,9 +39,9 @@ This solution that allows user to:
39
39
40
40
This article provides you with the information you need to configure wildcard application publishing in your environment.
41
41
42
-
## Charactrisitics of application segment(s) for complex application.
42
+
## Characteristics of application segment(s) for complex application.
43
43
1. Application segments can be configured only for a wildcard application.
44
-
2. External and alternal URL should match the wildcard external and alternal URL domain of the application respectively.
44
+
2. External and alternate URL should match the wildcard external and alternate URL domain of the application respectively.
45
45
3. Application segment URL’s (internal and external) need to maintain uniqueness across complex applications.
46
46
4. CORS Rules (optional) can be configured per application segment.
47
47
5. Access will only be granted to defined application segments for a complex application.
0 commit comments