gehorvath

Micro Focus Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-10-15
10:28
1295 views
GW ldap address book and Admin Defined fields
Hello,
I try to create a web based address book, based on the data in GroupWise. To accomplish this, I've enabled LDAP on one of the Domains. When I do a search, I don't see the Admin Defined fields in the result. Is this normal? How can I get the Admin Defined fields over LDAP? These fields contains important informations for the company.
Thx,
Gellért
I try to create a web based address book, based on the data in GroupWise. To accomplish this, I've enabled LDAP on one of the Domains. When I do a search, I don't see the Admin Defined fields in the result. Is this normal? How can I get the Admin Defined fields over LDAP? These fields contains important informations for the company.
Thx,
Gellért
3 Replies
buckesfeld

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-10-17
06:54
gehorvath,
admin defined fiels correspond to LDAP fields in your directory service. I'd rather configure LDAP in your directory and see if the fields show up when you contact an eDir/AD server. I'm using a simple PHP script on a web server to do something similar. Groupwise is out of the game here.
Uwe
--
Micro Focus Knowledge Associate
admin defined fiels correspond to LDAP fields in your directory service. I'd rather configure LDAP in your directory and see if the fields show up when you contact an eDir/AD server. I'm using a simple PHP script on a web server to do something similar. Groupwise is out of the game here.
Uwe
--
Micro Focus Knowledge Associate
gehorvath

Micro Focus Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-10-17
10:11
Hello Uwe,
Currently I use an open source ldap address book from sourceforge.net and I really like its features, IMHO it is better the GW address book, and user without access to GW can search the directory. It is attached to eDirectory. The problem is the data source. Since GW is now directory independent, most of the GW groups, and every resource, nickname is not in eDir. Beside this, if a users visibility is set to NONE, eDir does not know about this and the user is displayed. And of course none of the external users are displayed. All of these problems could be solved with the LDAP server build into GW. Unfortunately the admin defined fields are not in GW LDAP. So I fall between two stools again.
Sounds like an idea to the portal, or I have to merge GW and eDir LDAP source into a third LDAP source.
Gellért
Currently I use an open source ldap address book from sourceforge.net and I really like its features, IMHO it is better the GW address book, and user without access to GW can search the directory. It is attached to eDirectory. The problem is the data source. Since GW is now directory independent, most of the GW groups, and every resource, nickname is not in eDir. Beside this, if a users visibility is set to NONE, eDir does not know about this and the user is displayed. And of course none of the external users are displayed. All of these problems could be solved with the LDAP server build into GW. Unfortunately the admin defined fields are not in GW LDAP. So I fall between two stools again.
Sounds like an idea to the portal, or I have to merge GW and eDir LDAP source into a third LDAP source.
Gellért
buckesfeld

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-10-17
10:59
gehorvath wrote on 17.10.2016 11:16:
> Sounds like an idea to the portal, or I have to merge GW and eDir LDAP
> source into a third LDAP source.
Now that I understand your problem, I don't see any better solution 😕
Uwe
--
Micro Focus Knowledge Associate
> Sounds like an idea to the portal, or I have to merge GW and eDir LDAP
> source into a third LDAP source.
Now that I understand your problem, I don't see any better solution 😕
Uwe
--
Micro Focus Knowledge Associate