12-08-2014
Replacing NIS and RFC2307
Last year I posted I had written some new internet drafts designed to replace NIS and which would be the next evolution of RFC2307 (a standard describing how to represent NIS data in LDAP).
DBIS is now a reality. I have just completed a fully working reference implementation, and I would encourage anyone who works with NIS or the same data in LDAP to take a look and try it out:
dbis | SourceForge.net
DBIS brings with it a number of advantages, but its greatest feature (I think) is its ability to pull together a map from multiple locations in LDAP optionally applying transformations and conditions dynamically. This means, for example, that different business groups in your organisation can have tailored maps, but from a single source. You could have entries that only appear on a subset of hosts, or entries that are edited to look slightly different on a group of hosts. This also means there is more flexibility in the way you define your maps, so rather than having the content of a single map in one place, you can split them by business group or function. This could underpin a self-service application, for example.
DBIS builds on to the LDAP schema first introduced by RFC2307 but crucially does not modify any of the original definitions. It is therefore quite easy to migrate from RFC2307 to DBIS or run DBIS alongside RFC2307 on the same LDAP server. It is more closely compatible with NIS, esp. in respect to case sensitivity, meaning that it should also be easier to migrate from NIS to DBIS than it was to migrate from NIS to RFC2307.
Best regards,
Mark.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Discussion started by: larry
2 Replies
2. IP Networking
Hello together.
Is there someone who is able to explain me the differences between NIS and NIS+.
thanks in advance
joerg (2 Replies)
Discussion started by: joerg
2 Replies
3. 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
4. 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
5. Solaris
i want to dedicate my nis client system to some perticler group users.
how can it possible on solaris. (0 Replies)
Discussion started by: nag.mi2000
0 Replies
6. 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
7. UNIX for Dummies Questions & Answers
Hello i have some account already defined on NIS server. I would like to use this account on my machine.
What do i have to do ? Only create the home directory then use the account ??
If the user defined is using the korn shell, and i want to use bash, how can i change it ?? (2 Replies)
Discussion started by: dolphin06
2 Replies
8. 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
9. Linux
Hi All,
I have configured NIS server in linux rhel5 and made one client member to that server.
nfs share created for users home directory
i have created one nis user, user not able to change the passwd of his login.
getting below mentioned error
" yppasswdd not running on NIS master... (1 Reply)
Discussion started by: vinay_ks
1 Replies
10. UNIX for Advanced & Expert Users
I've released a set of new Internet Drafts that describe DBIS: an alternative to NIS and to the RFC2307 schema that has been used to date for representing NIS data in an LDAP Directory Server.
I'm writing a number of articles over the weeks further explaining the benefits of DBIS, and will also... (2 Replies)
Discussion started by: cambridge
2 Replies
LEARN ABOUT MOJAVE
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)