Sponsored Content
Full Discussion: Ldap sasl gssapi
Operating Systems HP-UX Ldap sasl gssapi Post 302886250 by Linusolaradm1 on Thursday 30th of January 2014 09:32:16 AM
Old 01-30-2014
Ldap sasl gssapi

I have installed all packages required(openldap,kerberos,cyrus-sasl)
configured ldap.conf
but when i did ldapsearch -Y gssapi return
Code:
ldapsearch -Y gssapi -H ldap://ldapserver-d -1  cn=prova

it did
Code:
ldap_msgfree
ldap_err2string
ldap_sasl_interactive_bind_s: Unknown authentication method (-6)
        additional info: SASL(-4): no mechanism available: No worthy mechs found

What i miss?
Thanks

Last edited by Franklin52; 01-30-2014 at 10:35 AM.. Reason: Please use code tags
 

7 More Discussions You Might Find Interesting

1. Solaris

LDAP client config GSSAPI

Configure ldap client: I have configured my ldapclient with the AuthenticationMethod=simple and with the credentialLevel=proxy. However, as soon as i want to set the AuthenticationMethod=sasl/GSSAPI, and credentiallevel=self, then it fails to configure. Kerberos is already setup successfully. The... (0 Replies)
Discussion started by: Henk Trumpie
0 Replies

2. Red Hat

Please help: Rhel5.6 and ldap+sasl

On Debian i set my ldap server,using tls and all works ok. On Redhat i have set my ldap server,using tls ok...but when i try to use ldapsearch without -x and with rootpw(created with slappasswd) it ask for sasl password! The question is: is possible to disable sasl? Thanks (2 Replies)
Discussion started by: Linusolaradm1
2 Replies

3. Red Hat

GSSAPI Error FTP

Hi Experts, While trying ftp from newly setup Linux box it is giving following error. GSSAPI error major:Unspecified GSS failure.Minor code may provide more information GSSAPI error minor:Unknown code krb5 195 GSSAPI error:initializing context GSSAPI authntication failed 504 AUTH... (1 Reply)
Discussion started by: sai_2507
1 Replies

4. UNIX for Dummies Questions & Answers

Configure Cyrus SASL NTLM Plugin with Postfix

Hello I hope somebody can help with this. I have a shell, that in case of failure, sends an email (relaying through an Exchange Server). This Exchange server only offers NTLM authentication. 250-AUTH NTLM This is the configuration I have: Postfix 2.1.1 as client. Cyrus-SASL... (1 Reply)
Discussion started by: viktor1985
1 Replies

5. Shell Programming and Scripting

Configure Cyrus SASL NTLM Plugin with Postfix

Hello I hope somebody can help with this. I have a shell, that in case of failure, sends an email (relaying through an Exchange Server). This Exchange server only offers NTLM authentication. 250-AUTH NTLM This is the configuration I have: Postfix 2.1.1 as client. Cyrus-SASL... (1 Reply)
Discussion started by: viktor1985
1 Replies

6. Slackware

Dovecot on Slackware14: gssapi auth

I have a postfix/dovecot mail server. On centos6 works great,sso with gssapi on linux and windows clients. On Slackware i have problems,Linux clients(thunderbird and mutt) connect ok,but not windows clients. on logfile only this Apr 19 19:01:41 cluster1 dovecot: auth: Debug: auth client... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

7. HP-UX

Disable GSSAPI when using an FTP client?

We have two HP-UX machines, both are B.11.31. When I FTP from the HP-UX boxes to a remote IBM server,- HP-UX 1: Connected to xxxx. 220-FTPD1 IBM FTP CS V1R12 at R2, 12:24:39 on 2013-08-30. 220 Connection will close if idle for more than 15 minutes. Name (xxxx:user): HP-UX 2:... (2 Replies)
Discussion started by: CaptNemo
2 Replies
PKCSICSF(1)							   openCryptoki 						       PKCSICSF(1)

NAME
pkcsicsf - configuration utility for the ICSF token SYNOPSIS
pkcsicsf [-h] [-l|-a token name] [-b BINDDN] [-c client-cert-file] [-C CA-cert-file] [-k privatekey] [-m mechanism] [-u URI] DESCRIPTION
The pkcsicsf utility lists available ICSF tokens and allows user to add one specific ICSF token to opencryptoki. The ICSF token must be added first to opencryptoki. This creates an entry in the opencryptoki.conf file for the ICSF token. It also creates a token_name.conf configuration file in the same directory as the opencryptoki.conf file, containing ICSF specific information. This information is read by the ICSF token. The ICSF token must bind and authenticate to an LDAP server. The supported authentication mechanisms are simple and sasl. One of these mechanisms must be entered when listing the available ICSF tokens or when adding an ICSF token. Opencryptoki currently supports adding only one ICSF token. The system admin can either allow the ldap calls to utilize exisiting ldap configs, such as ldap.conf or .ldaprc for bind and authentica- tion information or set the bind and authentication information within opencryptoki by using this utility and its options. The information will then be placed in the token_name.conf file to be used in the ldap calls. When using simple authentication, the user will be prompted for the racf password when listing or adding a token. OPTIONS
-a token name add the specified ICSF token to opencryptoki. -b BINDND the distinguish name to bind when using simple authentication -c client-cert-file the client certificate file when using SASL authentication -C CA-cert-file the CA certificate file when using SASL authentication -h show usage information -k privatekey the client private key file when using SASL authentication -m mechanism the authentication mechanism to use when binding to the LDAP server (this should be either simple or sasl) -l list available ICSF tokens -h show usage information FILES
/etc/opencryptoki/opencryptoki.conf the opencryptoki config file containing token configuration information /etc/opencryptoki/token_name.conf contains ICSF configuration information for the ICSF token SEE ALSO
opencryptoki(7), pkcsslotd(8). pkcsconf(8). 3.0 April 2013 PKCSICSF(1)
All times are GMT -4. The time now is 03:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy