Sponsored Content
Operating Systems HP-UX Problem in Configuring kerberos Server on HPUX Post 302616043 by vbe on Friday 30th of March 2012 11:39:00 AM
Old 03-30-2012
What did you type ? kdb_create -s ?
Did you execute the krb5_encrypt first ?
 

9 More Discussions You Might Find Interesting

1. Programming

Problem with kerberos cpp project

Hi All, I am having problem with kerberos kadmin library in c++. I am using red hat linux Enterprise Linux Server release 5 (Tikanga), and gcc c++ - 4.1.1-52.el4.i386. When I make a c project (main.c) and use function from kadmin library such as kadm5_init_krb5_context(&context); ... (2 Replies)
Discussion started by: amitp
2 Replies

2. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

3. Red Hat

PAM configuration: Kerberos authentication and NIS authorization problem

Hi, I've configured two linux boxes to authenticate against Windows Active Directory using Kerberos while retrieving authorization data (uids, gids ,,,)from NIS. The problem I ran into with my PAM configuration is that all authentication attempts succeed in order.i.e. if someone tried his... (0 Replies)
Discussion started by: geek.ksa
0 Replies

4. Solaris

LDAP Problem during Kerberos setting for Win server 03 Active Directory

Hi, FYI, I'm new in Solaris I'm trying to use Kerberos on authenticating LDAP Client with the Active Directory on Windows Server 2003 on both Solaris 10 5/08 and Solaris 10 9/10 by referring to the pdf file kerberos_s10.pdf available at sun official site. ... (0 Replies)
Discussion started by: chongzh
0 Replies

5. AIX

SSH and kerberos authentication problem AIX 5.3

I've configured an AIX 5.3 client to use our Windows AD for user authentication via Kerberos. When I try to ssh to the server using the AD credentials, I eventually get access but not after getting prompted for a password 3 times (which doesn't work) followed by an accepted login on the 4th... (3 Replies)
Discussion started by: jmroderick
3 Replies

6. Red Hat

Kerberos Test Server for training purposes

Dear all I am appearing for the RHCE exam next week (wish me luck). While training for the exam, i am supposed to configure the client to log on using an LDAP server that is also using TLS and Kerberos for authentication. Server setup is not included in the exam requirements only the client... (7 Replies)
Discussion started by: abohmeed
7 Replies

7. Solaris

Facing problem in configuring syslog server in Solaris

I am trying to configure central syslog server On hostA, in /etc/syslog.conf file,I am adding below line*.err;kern.debug;daemon.notice;mail.crit @hostB then I am restarting syslog servicesvcadm restart /system/system-log In hostA, I have already added hostB entry in /etc/hosts... (5 Replies)
Discussion started by: amity
5 Replies

8. Red Hat

/etc/rc2.d/ check if kerberos server is enabled in the log or not

Hi, I tried to execute a command to check if Kerberos server is enabled Printer Daemon is enabled GUI Login is enabled, do advise how I check from the logs below on how to check whether the commands are valid or not? ls -all /etc/rc2.d/ total 8 drwxr-xr-x. 2 root root... (2 Replies)
Discussion started by: alvinoo
2 Replies

9. UNIX for Advanced & Expert Users

Authenticating with SSSD / Kerberos against Windows Server 2012 R2

I'm authenticating with SSSD / Kerberos against Windows Server 2012 R2. I've setup credentails delegation using these options: Host * GSSAPIAuthentication yes GSSAPIDelegateCredentials yes GSSAPITrustDns yes For both client/server but no luck. I've read online that I need to run... (2 Replies)
Discussion started by: Devyn
2 Replies
LDAP_BIND(3)						     Library Functions Manual						      LDAP_BIND(3)

NAME
ldap_bind, ldap_bind_s, ldap_simple_bind, ldap_simple_bind_s, ldap_kerberos_bind_s, ldap_kerberos_bind1, ldap_kerberos_bind1_s, ldap_ker- beros_bind2, ldap_kerberos_bind2_s, ldap_unbind, ldap_unbind_s - LDAP bind routines SYNOPSIS
#include <ldap.h> int ldap_bind(ld, who, cred, method) LDAP *ld; char *who, *cred; int method; int ldap_bind_s(ld, who, cred, method) LDAP *ld; char *who, *cred; int method; int ldap_simple_bind(ld, who, passwd) LDAP *ld; char *who, *passwd; int ldap_simple_bind_s(ld, who, passwd) LDAP *ld; char *who, *passwd; int ldap_kerberos_bind_s(ld, who) LDAP *ld; char *who; int ldap_kerberos_bind1(ld, who) LDAP *ld; char *who; int ldap_kerberos_bind1_s(ld, who) LDAP *ld; char *who; int ldap_kerberos_bind2(ld, who) LDAP *ld; char *who; int ldap_kerberos_bind2_s(ld, who) LDAP *ld; char *who; int ldap_unbind(ld) LDAP *ld; int ldap_unbind_s(ld) LDAP *ld; DESCRIPTION
These routines provide various interfaces to the LDAP bind operation. After a connection is made to an LDAP server using ldap_open(3), an LDAP bind operation must be performed before other operations can be attempted over the conection. Both synchronous and asynchronous ver- sions of each variant of the bind call are provided. There are three types of calls, providing simple authentication, kerberos authentica- tion, and general routines to do either one. All routines take ld as their first parameter, as returned from ldap_open(3). SIMPLE AUTHENTICATION
The simplest form of the bind call is ldap_simple_bind_s(). It takes the DN to bind as in who, and the userPassword associated with the entry in passwd. It returns an LDAP error indication (see ldap_error(3)). The ldap_simple_bind() call is asynchronous, taking the same parameters but only initiating the bind operation and returning the message id of the request it sent. The result of the operation can be obtained by a subsequent call to ldap_result(3). KERBEROS AUTHENTICATION
If the LDAP library and LDAP server being contacted have been compiled with the KERBEROS option defined, Kerberos version 4 authentication can be accomplished by calling the ldap_kerberos_bind_s() routine. It assumes the user already has obtained a ticket granting ticket. It takes who, the DN of the entry to bind as. This routine does both steps of the kerberos binding process synchronously. The ldap_ker- beros_bind1_s() and ldap_kerberos_bind2_s() routines allow synchronous access to the individual steps, authenticating to the LDAP server and DSA, respectively. The ldap_kerberos_bind1() and ldap_kerberos_bind2() routines provide equivalent asynchronous access. GENERAL AUTHENTICATION
The ldap_bind() and ldap_bind_s() routines can be used when the authentication method to use needs to be selected at runtime. They both take an extra method parameter selecting the authentication method to use. It should be set to one of LDAP_AUTH_SIMPLE, LDAP_AUTH_KRBV41, or LDAP_AUTH_KRBV42, to select simple authentication, kerberos authentication to the LDAP server, or kerberos authentication to the DSA, respectively. ldap_bind() returns the message id of the request it initiates. ldap_bind_s() returns an LDAP error indication. UNBINDING
The ldap_unbind() call is used to unbind from the directory, terminate the current association, and free the resources contained in the ld structure. Once it is called, the connection to the LDAP server is closed, and the ld structure is invalid. The ldap_unbind_s() call is just another name for ldap_unbind(); both of these calls are synchronous in nature. ERRORS
Asynchronous routines will return -1 in case of error, setting the ld_errno parameter of the ld structure. Synchronous routines return whatever ld_errno is set to. See ldap_error(3) for more information. SEE ALSO
ldap(3), ldap_error(3), ldap_open(3) 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. OpenLDAP 2.0.27-Release 22 September 1998 LDAP_BIND(3)
All times are GMT -4. The time now is 04:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy