One of the many ways to achieve LDAP SSO using Delivery Server 10.1

Have you ever tried to Single Sign-On LDAP users into Delivery Server projects? Last week I was looking for a quick and easy method, with special assistance from Tim Davis (and thank you!), here I am documenting the steps to achieve this.

My solution can be explained in the simple diagram below:

Solution Architecture

As you can read from the diagram, I am using .NET to read the user name, format my own digest string, and then include hash value as one of the request parameters in the URL before getting redirected to Delivery Server by ISAPI. Once the request has traveled to Delivery Server, I can then use the username provided in the URL, compute and compare the hash values; if the hash values match then I can use dynament code to login the user automatically using the trusted mode.

Step 1 – writing  .NET code
This one is easy, very straight forward; a few variables, one function, one redirect.

FUNCTION_PAGELOAD

At the end of the Page_Load, I redirect the user request to a virtual directory I made up with the same name as the Delivery Server project name (just to make the URL user friendly).

Read more of this post

Advertisements

Troubleshooting Common Search with Delivery Server [Best Practice Project]

I went through the post blogged by Danny Baggs over and over again for about more than 10 times while setting up my Common Search server but it was just not working! There is nothing more frustrating than having the search working in Livelink but not in Delivery Server. I am new to the whole LiveLink interface thing and that didn’t help me either. If you are on the same boat and are having similar issues, I hope this post will assist a little.

From reading Danny’s post, we all know that we need to set up a shared folder and a Delivery Server connector to communicate with Common Search server. Here is the summary of what I’ve concluded after my 3 day’s tough time in regarding to how the integration works.

Delivery Server creates xml files which contain all the information about pages and project content, those files are stored under the shared folder for the Common Search Server to process; therefore, both servers need permission to write and read contents in this shared folder. The Common Search Server then indexes the files created by Delivery Server, creates a collection and sets up a search scope for each project . When a search query is performed, Delivery Server sends a request to the Common Search Server, the search query gets executed, and returned to the Delivery Server Server in the XML file format.

Easy, yeah?

So, here we set up the Delivery Server Connector, and I want to use my own Common Search user but not the Admin Account.

First tip, make sure the user has the “System Administration Rights“. This can be configured in the Common Search Interface. Read more of this post

OpenText Social Communities Installation + Integration with MS SSO

I have to say, I struggled with this for a good few weeks. Since the Delivery Server 10.1 is out with the Social Communities included, we have been asked many times to demonstrate it to our clients. Potentially, huge money there. However, the support to get this up and working is very limited.

I will try and make this really short, so that I don’t bore you to death.

Step 1

As always, make sure you have the required licenses, assuming you already have a working instance of Delivery Server 10.1. There are three modules that you will need, which are

  • HTRE – HTTP REST Connector
  • PCON – Portlet Connector
  • PRDW – Interface to JSR 168 and IBM WebSphere portlets

The OpenText licensing department seems pretty efficient in issuing/renewing licenses these days, which is good to see.

If you can’t get those required licenses, you will not be able to continue.

Step 2

You will need to install Common Search which now comes free with the Delivery Server.  (Make sure you have the license key too) You will need to do this before installing the Collaboration Server.

Step 3

We now need a Collaboration Server. Collaboration Server can be downloaded from the OpenText Knowledge Center along with the installation manual. You will need to follow the instructions carefully, as well as setting up the correct permissions for the indexing folder/s.

A successful install should get you the screens like below.

Collaboration Login Screen
Collaboration Login Screen
Collaboration Interface Screen
Collaboration Interface Screen

Step 4 Read more of this post