- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS<->LDAP Gateway, referrals, a distributed LDAP ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2002 01:03 AM
01-28-2002 01:03 AM
NIS<->LDAP Gateway, referrals, a distributed LDAP directory and bad headache.
a) its OWN ldap server
b) its OWN nis<->ldap gateway,
but any given user should be able to login on
ANY workstation ANYWHERE in the network;
or to put it more simple, If I did 'ypcat passwd' on ANY machine ANYWHERE I want to see all accounts from all over the company...
In theory, I'd set up smart referrals or default referrals inside the ldap tree, so that
any ldap server would point to his 'superior' when asked something he doesn't know.
But as I tried this approch, the gateway
doesn't follow those referrals at all, and it follows referrals into subtrees only
sluggishly, and not always...
As it is an experimental installation so far, all ldap servers concerned are on the same
host, running on different high ports.
I also tried the approach to set up a 'parent domain' in ypldapd.conf but that didn't help either..
any hints for me
bye,
M.Homann
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2002 05:53 AM
01-29-2002 05:53 AM
Re: NIS<->LDAP Gateway, referrals, a distributed LDAP directory and bad headache.
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2002 12:08 AM
01-30-2002 12:08 AM
Re: NIS<->LDAP Gateway, referrals, a distributed LDAP directory and bad headache.
been there.. done that...
boss says 'no way, no single point of failure'. Besides, the departments are NOT at the same location, so this way would make the ldap queries travel around the world via WAN lines...
bye
MH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2002 12:47 AM
01-30-2002 12:47 AM
Re: NIS<->LDAP Gateway, referrals, a distributed LDAP directory and bad headache.
even when I have the nis<->ldap gateway software connect to the topmost ldap server it doesn't follow referrals, but a shell-issued ldapsearch does...
bye
MH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2002 02:15 AM
01-30-2002 02:15 AM
Re: NIS<->LDAP Gateway, referrals, a distributed LDAP directory and bad headache.
hosts a and b; host a has 4 DS4 instances on different ports, built into a tree via smart referrals.
When I do ldapsearch with the ldap tools from that nis<->ldap gateway, this happens:
when I do it on the same machine that runs the DS4 instances, it follows the referrals down to the last branch.
when I do it on the other machine, it only sees entries in the top-level ldap server.