06-23-2009
NIS+ to LDAP
After months of threats, we're finally migrating servers from NIS+ to LDAP.
I'm happy using niscat, nisgrep etc and now it seems I have to use ldapsearch which is far from being a simple CLI!
Are there any easy (easier?) ways to interrogate the LDAP directory?
Jerry
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I am a solaris administrator who is currently working in a solaris 2.6,7,8,9 environment. We are using NIS for centralised account authentication, groups, host name resolution and most importantly automounting. NIS , over the last few months has been rearing its notorious ugly head, and to be... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I just took over the admin role from someone and I wanna setup sendmail (just to send mail from the host) however, after I config all the resolv.conf, nssitch.conf, hosts file and when I try to send a mail out, after I punched ctl-D, it returned he following,
"NIS map mail.aliases... (2 Replies)
Discussion started by: stancwong
2 Replies
3. UNIX for Advanced & Expert Users
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies
4. Solaris
Hi, all.
I have a Solaris client here needs to bind to NIS server in another subnet. Following is the configuration i made on the client,
1) edit /etc/inet/hosts to add an entry of the NIS server -- nserver01
2) execute `domainname` to set local NIS domain to the domain of the NIS server.... (1 Reply)
Discussion started by: sn_wukong
1 Replies
5. HP-UX
Hello All,
I am a newbee in HP UX wanted to know how to configure DNS,NFS,NIS,LDAP and LVM(mirror,sparing and multipathing) in HP UX 11iv2 and v3 and i did go through some of the docs on hp.com but i think those are for experience UX users and i am new to this so if some one could just mention... (1 Reply)
Discussion started by: coolsami
1 Replies
6. Shell Programming and Scripting
I'm creating a scrip for auditing our AIX box's to ensure that they are built according to our system standards. I'm not sure on the logic for checking to see if the NIS and NIS+ services are disabled. any idea's? (2 Replies)
Discussion started by: sport
2 Replies
7. UNIX for Advanced & Expert Users
I've recently published a set of tools that allow you to continue to use the ypwhich, ypcat and ypmatch tools in an environment where NIS maps have been migrated to LDAP using the RFC2307 schema.
Traditionally in such an environment, only the NSS functionality is LDAP-enabled, meaning that... (0 Replies)
Discussion started by: cambridge
0 Replies
8. Cybersecurity
Hi guys,
we are implementing new ldap in our organization exclusively for Linux authentication purposes. As we are new to the subject, I would appreciate help regarding which schema to use to create group of users and accounts / passwords entries? I see both schemas listed in subject above... (0 Replies)
Discussion started by: Lastminute
0 Replies
9. UNIX for Advanced & Expert Users
I have some scripts where I go and do some LDAP/NIS queries to report on users on Unix servers. What I am trying to figure out is, how do I know which server is the LDAP? The configs have been in place long before I took over so was hoping someone had some insight on how to figure this out. I must... (1 Reply)
Discussion started by: dagamier
1 Replies
10. Solaris
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
LEARN ABOUT SUSE
ypmap2src
ypmap2src(1M) System Administration Commands ypmap2src(1M)
NAME
ypmap2src - convert NIS maps to NIS source files
SYNOPSIS
/usr/lib/netsvc/yp/ypmap2src [-t] [ [-c custom-map-name]...] [-d domain] -o output-directory [ [ source-file]...]
DESCRIPTION
Use the ypmap2src utility to convert standard NIS maps to approximations of the equivalent NIS source files. This utility functions like
the reverse of ypmake(1M).
The primary use for ypmap2src is to convert from a NIS server that uses the NIS to LDAP(N2L) transition mechanism, which does not use NIS
source files, to traditional NIS, where source files are required. The ypmap2src utility is also used by NIS administrators who wish to
discover the contents of NIS maps for which the sources are not available.
Generally, this operation is not necessary. More often, administrators will switch from traditional NIS to N2L in anticipation of the even-
tual transition to LDAP naming. When this switch is made, authoritative information is moved into the LDAP DIT, and the NIS sources have no
further role. N2L supports NIS clients until such time as they can be converted to LDAP, and the NIS service suspended.
The ypmap2src utility does not guarantee that the files that are generated are identical to the original NIS source files. Some information
might have been thrown away by ypmake and cannot be recovered. N2L also might have updated the maps to reflect changes made by LDAP
clients. It is essential that the sources generated are checked to confirm no problems have occurred.
Per entry comment fields, from existing source files, are not merged into source files generated by ypmap2src. If a user wishes N2L to
maintain comment information, then the NISLDAPmapping configuration file should be modified so that the comment fields are mapped into
LDAP. This will ensure that the comments are visible to native LDAP clients and present in the N2L map files.
When ypmap2src is run, it will take up-to-date comments from the map file and insert them into the NIS source file generated.
Handling Custom Maps
ypmap2src only knows about the standard NIS maps and standard source to map conversion. If an advanced user has changed these, that is, the
user has modified the NIS makefile, the equivalent changes must also be made to the ypmap2src script.
OPTIONS
ypmap2src supports the following options:
-c Specifies that custom-map-name should be converted to a source file by running makedbm -u on it. This is a short cut
so that simple custom maps can be handled without editing ypmap2src.
-d domain-name Specifies the domain to convert. The domain-name can be a fully qualified file path, such as /var/yp/a.b.c, or just a
domain name, a.b.c. In the latter case, ypmaptosrc looks in /var/yp for the domain directory.
-o dest Specifies the destination directory for the converted files. A directory other than /etc should be specified. The maps
generated are copied to the correct location, /etc, /etc/security or other source directory, as appropriate.
-t Specifies that traditional NIS maps, without N2L's LDAP_ prefix, should be converted. By default, maps with the LDAP_ pre-
fix are converted.
OPERANDS
ypmap2src supports the following operands:
source-file Lists the standard source files to convert. If this option is not given, then all the standard source files, plus any cus-
tom files pecified by the -c option, are converted.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWypu |
+-----------------------------+-----------------------------+
|Interface Stability |Obsolete |
+-----------------------------+-----------------------------+
SEE ALSO
ypmake(1M), ypserv(1M), NISLDAPmapping(4), attributes(5)
System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)
SunOS 5.10 10 Apr 2003 ypmap2src(1M)