Liberty Enabled Portal Samples This directory
contains samples for Liberty Enabled Portal Server. Below is the short
description of each sample.
Sample 1: This sample uses 2
machines, one for IDP running only IS and the other for SP running
Portal Server. Authentication-less desktop is disabled. Federated users
who are already liberty signed-on are presented personalized desktop
when they access the portal desktop, while those who are not liberty
signed-on are redirected to the IDP's authentication page. User's
without any Identity federation are presented the local login page if
they are not locally signed-on.
Sample 2: This sample uses 2
machines, one for IDP running only IS and the other for SP running
Portal Server.
This sample is different from sample 1 in only one aspect, i.e.
Authentication-less desktop is enabled. So, users without any Identity
federation and not locally signed-on will see authentication-less
desktop, while the federated users are redirected to the IDP
authentication page when they access the portal desktop and if they are
not liberty signed-on. The federated and liberty signed-on users will
see the personalized desktop without any need for further authentication.
Sample 3: This sample uses 2
machines, one for IDP running only IS and the other for SP running
Portal Server.
This sample is different from sample 1 in that the Authentication-less
desktop is enabled. It is different from sample 2 in that the
Authentication-less desktop access is enabled for federated users. So,
federated users who are not liberty signed-on will also see the authless
desktop. The login channel will show a link "Federated users click
here". Federated users can perform a liberty login by clicking this
link. The users who are liberty signed-on will see the personalized
desktop. The Common Login channel will also be displayed on the authless
desktop which contains a list of available IDPs (only one in this case).
Federated user may also click on an IDP in the common login channel to
do liberty login.
Sample 4: This sample uses 2
machines, one for 2 IDPs running on one IS and the other for SP running
Portal Server.
Because there are more than one IDP, the Common Domain Service (CDS) is
used to read/write common domain cookie for the user. The common domain
cookie is used to find the preferred IDP for the user. This CDS may be
installed on any of the 2 machines or on a separate third machine. In
this sample, it will be run on the machine hosting the SP.