This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 35 lines
!!! Overview
[{$pagename}] architectures is where all web requests are routed through the [Proxy Server].
Access to the back-end [HTTP]-Application servers can only be accessed via the [{$pagename}].
[{$pagename}] can provide a more universal integration with [HTTP] servers since the common standard protocol, HTTP, is used instead of vendor-specific application programming interfaces (APIs).
[{$pagename}] acts as a contact point between the user's web [browser] and the [HTTP-Server] as a [Protected Resource].
The [{$pagename}] masks the protected web server by presenting different external [URLs] to the internal [URLs].
The [{$pagename}] becomes the communication point and can control access and carry out Single Sign-On operations. Ideally, it is not necessary to modify the protected application.
!! Advantages of [{$pagename}]
[{$pagename}] has several advantages:
* [{$pagename}] completely independent of the web servers, both technically and environmentally.
* Several [{$pagename}] implementations provide high availability and load balancing of the access points.
* Several [{$pagename}] implementations are able to consolidate WEB Server to appear as a single site.
** Applications served from two different WEB servers could appears as the same: willeke.com/cars and willeke.com/boats could be hosted on different servers.
* Several [{$pagename}] implementations allow administrative delegation so WEB Admins can alter their site configurations.
* Migration from one product to another is less impactful to the environment.
* No Agent installations or upgrades.
!! Drawbacks of [{$pagename}][1]
Nevertheless, this technology does have some drawbacks:
* The web application must be correctly written and contain clean URLs, and typically the URLs must be relative to the root of the website.
* Some reverse proxies only modify the HTTP headers and are not able to modify the HTML content of the pages.
* The advent of AJAX technologies and URL and Javascript modifications make it difficult for reverse proxies to analyse page links and reconstruct external URLs.
* The web application should not contain absolute links to other internal applications which are also accessible behind a reverse proxy.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [What is the Web SSO|http://www.evidian.com/products/web-sso/what-is-the-web-sso/|target='_blank'] - based on data observed:2015-05-18