Portion of Application Development with Single Sign-On presented at 2010 Developer Conference
ClientLib conceptually refers to a library that can be incorporated within an application both to access information passed to the application by the SSO Environment via injected headers and to ask policy questions of an openSSO policy server or Oracle Entitlements Server for fine-grained permissions such as selectively rendering portions of pages. Two versions are available. The ClientLib4J is a version for Java and includes JSP and JSF Facelets tag libraries allowing authorization and conditional rendering of blocks within pages. The ClientLib4X is used with Mark Logic application servers which use XQUERY as their scripting language.
Additionally, both provide support for crafting URLs in the canonical (internet) space of the application which may be distinct from the application URL space. For example, Java applications reside in a servlet container at a java context like nextgen-member. But suppose that upon rolling out to a Church web site it must reside at a context of /mls/mbr. The canonical space is the latter. The application space is the former. And URL rewriting must translate inbound calls before they reach the application server otherwise the application server will receive a request for /mls/mbr/... and won't be able to map it to the expected and necessary application context /nextgen-member. Similarly, links within application pages may need to be fully qualified for some reason. For example, search engines grant greater rank to fully qualified links in pages that they do to relative links. Since the application resides at a different context in the canonical internet space than it does in the application space URLs must be generated appropriatly. ClientLib provides such support.