Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 330 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LDAP-Authentification & Cobion

DV_Kaschke
LDAP-Authentification is not well explained in the documentation, also board-search does not realy help to solve this problem.

So far so good - I'm able to authenticate ASL against our NetWare-Server via LDAP. But if I want to use Cobion-Profiles I'm lost. How will I configure the LDAP Profile Assignment in the HTTP-Proxy?

I just created some NDS-Objects so now inside of the Userprofile I can see an Attribute with the LDAP-Browser looks like

Name: groupMembership
Value: cn=Standard,cn=HTTP,cn=ASL_AUTH,o=MyKontext

I created a profile "Standard" which shoud be validated against this Parameter. How should the "LDAP match DN" looks like?


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Xeno
    xeno,

    I'm glad I stumbled across this post! There is *no* mention of this in the documentation. After much head scratching, I finally got this to work!

    I don't think the profile names have to necessarily match the name of the NDS group - just the "LDAP match DN "

    I set up a "restricted " group and a "unrestricted" group in NDS, assigned users, set up a "restricted" and a "unrestricted" profile, and then - for the hard part - I assigned the profiles with the full ldap DN of the group. For example I used 
    "cn=filtered-web,ou=users,o=NOVELL" for my filtered group, and "cn=unrestricted-web,ou=users,o=NOVELL" for my unrestricted group.

    Finally I got this working!  [;)]

    Maybe this post can be of use to somebody else.....

    John Braner