Domain Trusts

Are you running LSF9 or Env 8.0 ?
Is this for portal authentication and/or the environment running on Windows?

I am sorry for not giving more information. I am actually suprised to have receievd a comeback on this one. But, LSF 9.0 and this is for portal authentication. We do use LDAP/Bind.

So, not for the environment itself, just for Portal?

Logging into the portal would be how they would access the environment correct? Or are there additional steps that I am missing. I thought thatthe portal access would be all that i needed but seems as though that i might need more. Your help with this matter is greatly appreciated.

If you Portal login is only for interactive/forms. What about batch users?

If you're running the environment on Windows, batch users are local machine or in a Windows domain. If you're running the environment on Unix, batch users are Unix users, and the only "domain" issue is their portal authentication.


No offense, but if you don't understand that part, you're probably out of your range of expertise, and should be getting some help with this...

No offense taken, skin tougher than that...we are running in a Unix enivironment. As I had stated earlier I thought that we would just need the portal authentication. If this is not the place to ask this question would you be able to direct me to some other place rather than Lawson because no one there seems to be able to give any direction. We were one of the first to run the entire LSF9.0 suite. We used LDAP bind before it was even supported by Lawson. I don't know everything about it, but I think that we can converse. It just has been challenging because I don't know of anyone that has the setup that we are looking for or has even attempted it. Again, any help would be greatly appreciated.

Oh, this is a good place to have the conversation...in fact, that's one of the reasons this site exists.

Since your running the environment on Unix, Portal authentication is all you would need to worry about.
You would need to re-run the ldapbind to query against a different search location / context within (i.e. higher up) in your AD tree/forest. You will need to make sure that the user that is specified for the ldapbind has query access against the forest.

Thank you. To re-run the ldapbind in a "different location" I understand but the domain trust is not as a parent child situation. The domain trust is set with another AD forest on the same level as ours. Are you saying that I would have to have a user with query access setup on the other domain for this to work? To clarify these domains are in completely separate forests. There is nothing higher up as they are on the same level. We have a forest level trust so that the users in the other domain can authenticate to other resources in our domain (ie: sharepoint).
Is it possible to bind to two separate domains?

You should be able to get ldapbind to search across multiple domains, provided you bind to an AD domain controller that is in the "global catalog" role for the forest (and instead of using ldap port use GC port 3268).

In addition, you will likely have duplicate username collisions across the multiple domains, so you will need to update all of the SSOP identities to include the domain, e.g. DOMAIN\username. Then in the ldapbind, specify %DOMAIN% as part of the search base--something like CN=Users,DC=%DOMAIN%,DC=com (i.e. the user logs in as DOMAIN\username, and SSO will pass the DOMAIN thru to ldapbind to authenticate them).

Thank you. I will try what you have suggested in our test environment and let you know what we get. John, I really appreciate everything you are doing here. The information that I received from the website has proved to be invaluable.Again, thanks for all you do.

Phil 4:23

Did you ever get this working? I have run across a similar issue, and the bind refuses to search the main tree because of a trusted domain. I ended up with a workaround of using ADAM passthru authentication, and binding to a separate ADAM instance that contains only the users who need access to Lawson.

I think that bind to the Global Catalog instead of just domain (different port number) may solve the issue. Global Catalog should search ALL domains in a forest, and if you have users only in some dmains, just put them in the LDAP filter in SSOP service.

Alex, sometimes I forget things....I can't believe I forgot this one! It works just fine!

Yes, we got it working...sorry for not responding earlier...