The Rough Guide to Configuring the Solaris KDC LDAP Backend


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS The Rough Guide to Configuring the Solaris KDC LDAP Backend
# 1  
Old 09-09-2008
The Rough Guide to Configuring the Solaris KDC LDAP Backend

Steps to configure a Solaris KDC and LDAP directory to store andretrieve Kerberos records from the LDAP Directory Server.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

Good and simple guide to configuring DHCP on Solaris 11?

I've been learning Solaris 11 for the past couple weeks and have been curious about setting up a DHCP server. Is there a good guide to start me off? Something pretty simple that I can understand? I read Oracle's documentation on it but I want something a little easier to understand. Thanks! (1 Reply)
Discussion started by: austinramsay
1 Replies

2. UNIX and Linux Applications

phonon-backend-gstreamer vs phonon-backend-vlc vs phonon-backend-xine

phonon-backend-gstreamer vs phonon-backend-vlc vs phonon-backend-xine What are the advantages and disadvantages of phonon-backend-gstreamer, phonon-backend-vlc, and phonon-backend-xine. I was reading this and got curious. ... (1 Reply)
Discussion started by: cokedude
1 Replies

3. Shell Programming and Scripting

need help on configuring LDAP server on solaris

HI All I need help to understand how the ldap works in Solaris 9 & Solaris 10. Kindly provide me some helpful commands related to LDAP Regards Jagan (2 Replies)
Discussion started by: jaganblore
2 Replies
Login or Register to Ask a Question
UD(1)							      General Commands Manual							     UD(1)

NAME
ud - interactive LDAP Directory Server query program SYNOPSIS
ud [-Dv] [-s server] [-d debug-mask] [-l ldap-debug-mask] [-f file] DESCRIPTION
ud is used to interogate a directory server via the Lightweight Directory Access Protocol (LDAP). OPTIONS
-s server Used to specify the name of an LDAP server to which ud should connect. If this flag is omitted, the value specified in the ud configuration file is used. If no value is specified in the configuration file, or the configuration file does not exist, the name ldap is used. Of course, it is up to the system administrator to make sure that the name ldap can be resolved (presumably through the use of a CNAME or A record in the DNS and the appropriate search path specified in the resolver config file). -d debug-mask Sets the ud debug mask to the value specified. Values for the mask can be dumped by using the -D flag. -f file Sets the configuration file to the name specified. -l ldap-debug-mask Sets the LDAP debug mask to the value specified. -v Turns on verbose output. Also toggable via the ud verbose command. -D Prints out a list of valid ud debug masks. FILES
/etc/openldap/ud.conf The ud configuration file. SEE ALSO
ud.conf(5), ldap.conf(5), ldap(3) DIAGNOSTICS
ud will try to be nice about error conditions, and in most cases prints a warm and fuzzy error message when it encounters a problem. Some- times the error will be unexpected, and in these cases, ud uses the ldap_perror() routine to print an informative diagnostic. BUGS
Too numerous to mention. AUTHOR
Bryan Beecher, University of Michigan ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release. 4.3 Berkeley Distribution 20 August 2000 UD(1)