IBM Security Access Manager for e-business uses junctions to identify web servers. The client's browser uses one set of URL links and the back-end web server uses another. In this white paper, learn how WebSEAL processes URLs from the back-end server and the client. This white paper by Ori Pomerantz you will learn:
- How WebSEAL, a proxy web server that is located between the Internet and the internal back-end servers, uses URLs, links, and junctions to enforce security policy. He defines relative, server-relative, and absolute link types.
- How WebSEAL can modify outbound links so they will work with the back-end servers.
- How WebSEAL handles absolute links and canonical names by converting the host name to an IP address and then back to a name.
- How to make WebSEAL peek in a script to modify absolute links.
- How WebSEAL uses junction cookies, the HTTP header referer, a junction mapping table, and transparent path junctions to identify the junction of inbound server-relative links.
- How WebSEAL uses virtual host junctions to identify the junction of inbound absolute links.