Using an Authentication Portal Landing Page

Follow

If desired, you can configure a specialized authentication portal landing page that will allow your site to provide both RemoteAuth and non-RemoteAuth logon options from a single link within a catalog or finding aid. Sites wanting to provide users with one link to various different logon options can use the Atlas Authentication Portal feature. The Atlas Authentication Portal application allows sites to provide a single link from a catalog or finding aid system that will take users to a page where they can select whether they log in via RemoteAuth or another method. In addition to providing logon links, this feature supports passing query string data through the portal to the selected destination. 

The application files needed for this feature are available as a zip file on the ILLiad 9.0 Downloads NEEDS UPDATING page. Alternatively, ILLiad Customer Service can supply the application to you and assist you with setup.

 

The specialized authentication portal landing page, Index.cshtml, displays instructional text to help sites configure the portal to look and work as desired. Once configured, this page will provide users the options for logging into ILLiad. When the user clicks the link and logs into ILLiad, the item data embedded in the original link is carried through and applied to the request form. This page is located in the AtlasAuthPortal file under \AtlasAuthPortal\Views\Portal.

Two Types of Access

There are two options available for configuring the portal: form based access and linked based access. The default authentication portal page explains in detail how each option works and how to configure either of these options for use by your site.

Automatic Redirect Feature

When the portal is invoked it supports cookie-based tracking of the options selected by the user. If the user is currently logged into the destination system and has previously gone through the portal, it will forward them to their destination rather than show them the selection screen again.

Installing the Atlas Authentication Portal Application

In order for the Atlas Authentication Portal to work properly, you must have Microsoft .NET 4.5.1 Framework installed on your ILLiad web server.

  1. Download the AtlasAuthPortal files and extract the folder to the web folder on the server (C:\inetpub\wwwroot\illiad is the default).
  2. Open the IIS Manager on your server.
  3. Navigate to AtlasAuthPortal by clicking Your Server Name | Sites | Default Web Site | ILLiad | AtlasAuthPortal.
  4. Right click on the Atlas Auth Portal and select Convert to Application.
  5. Accept the application defaults or make changes and click OK. The AtlasAuthPortal icon will change from a folder to an application icon.

Configuring the Atlas Authentication Portal

Once you have installed the Atlas Auth Portal application, there are two steps to set up the authentication portal feature.

  1. Modify the default portal page (Index.cshtml) using the instructions provided on the page. This page is located in the AtlasAuthPortal file under \AtlasAuthPortal\Views\Portal.
  2. Edit the Web.config file for the authentication portal to include the correct <appSettings> values for the SessionCookieName and UsePersistentRedirectCookie settings. This file is located in the AtlasAuthPortal file under \AtlasAuthPortal\Views.
    1. SessionCookieName value: ILLiadSessionID: This controls the cookie that should be looked for to identify whether or not the user is logged in. By default ILLiad stores the login as ILLiadSessionID.
    2. UsePersistentRedirectCookie value: true: This determines whether or not the cookie used to store the redirectURL the user selected on their last visit should be persistent or not (whether the cookie should be available after the user has closed their browser and come back to the portal).
    3. RedirectUrlCookieName: RedirectUrl: This specifies the name to use when storing the portal's redirect URL in a cookie. By default ILLiad stores the name as RedirectUrl. This can be changed to avoid conflicts between multiple instances of the Atlas Auth Portal on the same domain. For example, if a second instance of the Atlas Auth Portal is set up to redirect to the open URL action, its RedirectUrlCookieName might be set to OpenUrlRedirectUrl.

Because cookies are generally specific to the domain that they are created under, the Automatic Redirect Feature cannot be used unless both the Portal landing page and the ILLiad.dll (which generates the session cookie that the Portal is looking for) are both under the same domain. Therefore, the Portal landing page URL needs to have the same domain name as the resulting ILLiad DLL pages. Generally, all of these web pages are on the same server, but take care to use a consistent DNS name. Otherwise, the portal page will be set up correctly, but users will still have to pass through that page after having authenticated.

OpenURL links to ILLiad passing through the Atlas Authentication Portal will need to be edited to look like this:

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.