Page 1 of 1

Infosphere 11.5 - LDAP AD Authentication

Posted: Fri Aug 26, 2016 10:19 am
by skathaitrooney
Hello Experts,

We recently installed Infosphere 11.5 on our systems. It is a WAS standalone configuration. The engine and services tier are on the same computer.

We configured WAS admin console as described in the IBM docs to use LDAP.

https://www.ibm.com/support/knowledgece ... view=embed

We followed the steps as mentioned in the IBM notes. When we restarted WAS, we are able to login to WAS admin console using the LDAP userid, but when we try to login to the IIS consoles using the same WAS LDAP user id, it gives us an error saying that the User should have Suite User roles to proceed.

I even added my own LDAP id using the DirectoryAdmin tool as Administrator, but still it is popping up this same error.

Can anyone help me here?

Posted: Fri Aug 26, 2016 4:15 pm
by ray.wurlod
Can you view the WAS admin user within the Users panel of web console for Information Server? If so, does it have Suite User role?

Posted: Sun Aug 28, 2016 1:47 pm
by skathaitrooney
Thanks Ray for replying. The issue itself is that i am not able to login to IIS Console. Though the IBM product documentations mention that the WAS user id is by default granted an admin role when you switch to LDAP.
I tried listing out the access levels of the WAS admin id (the LDAP id) using the DirectoryAdmin tool, turns out all the access are intact for this id.
DataStageAdmin
FastTrackAdministrator
GlossaryAdmin
ISDAdministrator
MDWAdministrator
RulesAdministrator
SorcererAdmin
SuiteAdmin
SuiteUser

But when i try to login to IIS console, get an error stating that you need SuiteUser role to login :S

Posted: Mon Aug 29, 2016 3:51 am
by skathaitrooney
Also, i have a doubt that what would happen to the default datastage admin user - dsadm which is a local OS user and not an LDAP AD user ?

Will we still be able to use this user to login to DataStage clients ?

Posted: Thu Sep 01, 2016 9:14 am
by skathaitrooney
So IBM asked us to us LDAP using Federated Repositories. After switching to Federated Repositories our issue resolved.

IBM also said that they highly recommend Federated Repositories due to its scalability and ability to use multiple repositories.