Blog Network Home > Pitstop > Enterprise Applications > Part II – Peoplesoft and Microsoft Active Directory Single sign on Setup

Part II – Peoplesoft and Microsoft Active Directory Single sign on Setup

by Pon ArunKumar Ramalingam on June 9, 2008 in Enterprise Applications, Pitstop

Hip Hip Hurray !!!! 2 Lewis Hamilton Fans !!!!!

Its a dream run on monaco for his team. And it is also time for us to hit the fast track to part 2 of the single sign on between Microsoft and Peoplesoft,

Steps to perform on LDAP:
1. Access ldp.exe from within the Microsoft Active Directory
2. Connect to the LDAP server with the default port 389 (click on Connection->connect)
3. Click connection-> bind and enter the user account name and password
4. Click View->TreeView and enter the Base DN (DC=Helix,DC=Hexaware,DC=com)
5. Select the User Group present with the ldap, CN=Users, DC=Helix, DC=Hexaware, DC=com
6. Select the administrator listed down under the selected user group (e.g CN = Hexaware Admin, CN=Users, DC=Helix, DC=Hexaware, DC=com)

Sample Environment Used: DNS- Helix.Hexaware.com

Steps to do on Peoplesoft:
1. Navigate to PeopleTools > Security > Directory > Configure Directory
2. Create a New Directory ID
3. Select the directory product as ‘Microsoft Active Directory’
4. Enter the default connect DN (The steps are listed on the above section, e.g CN = Hexaware Admin, CN=Users, DC=Helix, DC=Hexaware, DC=com)
5. Enter the administrator password for the administrator user id ‘Hadminis’
6. Enter the LDAP Server Name and the default port 389
7. In the Additional Connect DN’s tab, enter the User DN “Helix\Hadminis” and its password
8. Now test the connectivity to get the success on all the sub sections.

Most Common Errors:
===================
1. User who is setting up the single sign on should be aware of the difference between the Administrator User ID and Its Canaonical Name
2. In Connectivity Failure – Use Network Analyzer Tool ( I will bring in more details in my next post)

Hope the start off steps helps ,.. Await more on Peoplesoft Schema Caching in pitstop’s next post.

You might want to read these awesome related posts


{ 7 comments }

1 Jamie B July 3, 2008 at 2:09 pm

I recenelty got his configured…. now the fun part is getting SSL working with an AIX app server running PT8.49 and Microsoft Active Directory.

2 Pon ArunKumar Ramalingam July 7, 2008 at 9:45 am

Thats great to hear Jamie , that you got this configured. So whats happening on the SSL and AIC ?

3 Prasanth Sadasivan October 16, 2008 at 8:19 pm

we have a 8.48.17 tools version, with active directory integrated; and infrastructure has more than one LDAP servers. is it possible to configure more than 1 LDAP server in PeopleSoft, what are the challenges in configuring

4 Pon ArunKumar Ramalingam October 27, 2008 at 2:00 pm

Yes, It is possible to configure more than one LDAP server in peoplesoft. The same procedue is followed with multiple LDAP servers.

5 ravi February 10, 2009 at 8:34 am

Hi Arun I am ravi,

I need some pointers on configuring PeopleSOft with a Directory Server. I work on user provisioning for a leading indentity management software. I do not have access to peoplesoft help. can you point to documentaion and online help to achieve my tasks.
Thanks,
Ravi

6 Pon ArunKumar Ramalingam February 10, 2009 at 9:37 am

Hi Ravi – Hope this helps,.. Check this Link And do follow the steps in this post.

7 Amit B November 26, 2009 at 11:05 pm

Hi,

If you point PeopleSoft to use AD authentication, I want to understand -
1) How will I authorize users for each transaction i.e. to provide access to each page, will PeopleSoft still refer to Database user ID or will it look at AD username? Or is AD integration like using alternate ID in Peoplesoft?

2) If there are transactions earlier stored with database user ID, then after changing to AD authentication, will all transaction logs be lost??

Your response can help.

Comments on this entry are closed.