HP Visualize b2000 hp enterprise file system: release note for hp DCE/9000 enh - Page 37

NIS and Integrated Login Interoperability

Page 37 highlights

Compatibility Information and Installation Requirements NIS and Integrated Login Interoperability NIS and Integrated Login Interoperability NIS, Integrated Login, and DCE/DFS should interoperate without any problems because they do not have any knowledge of one another. Both Integrated Login and NIS attempt to solve the problem of creating a common /etc/passwd and /etc/group file on multiple nodes. Integrated Login does this by using /opt/dce/bin/passwd_export to pull the contents of the DCE registry (basically the global /etc/passwd and /etc/group files) onto each node. NIS, on the other hand, gets the global /etc/passwd and /etc/group files through a hook in the getpwent() system call. DCE/DFS uses this functionality primarily to print a username and group when you perform an ls -l within DFS. The second function of Integrated Login, which NIS does not provide, is to obtain a user's DCE credentials when a user performs a standard UNIX login through telnet, ftp, CDE, etc. If Integrated Login obtains the credentials successfully, the user accesses DFS in an authenticated manner, and without having to perform a dce_login. When DCE is not available, Integrated Login falls back to using the /etc/passwd file; upon successful login, the user does not have DCE credentials, gains unauthenticated access to DFS, and thus can only access entries with an any_other ACL entry. 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40

37
Compatibility Information and Installation Requirements
NIS and Integrated Login Interoperability
NIS and Integrated Login Interoperability
NIS, Integrated Login, and DCE/DFS should interoperate without any
problems because they do not have any knowledge of one another.
Both Integrated Login and NIS attempt to solve the problem of creating a
common
/etc/passwd
and
/etc/group
file on multiple nodes. Integrated
Login does this by using
/opt/dce/bin/passwd_export
to pull the contents of
the DCE registry (basically the
global /etc/passwd
and
/etc/group
files)
onto each node. NIS, on the other hand, gets the global
/etc/passwd
and
/etc/group
files through a hook in the
getpwent()
system call. DCE/DFS
uses this functionality primarily to print a username and group when you
perform an
ls -l
within DFS.
The second function of Integrated Login, which NIS does not provide, is to
obtain a user's DCE credentials when a user performs a standard UNIX login
through
telnet
,
ftp
, CDE, etc. If Integrated Login obtains the credentials
successfully, the user accesses DFS in an authenticated manner, and without
having to perform a
dce_login
. When DCE is not available, Integrated Login
falls back to using the
/etc/passwd
file; upon successful login, the user does
not have DCE credentials, gains unauthenticated access to DFS, and thus can
only access entries with an
any_other
ACL entry.