[36710] in Kerberos
Re: Wrong principal in request error on gss_accept_sec_context()
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jan 5 17:12:12 2015
Message-ID: <54AB0C2A.90302@mit.edu>
Date: Mon, 05 Jan 2015 17:11:54 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: "Xie, Hugh" <hugh.xie@bankofamerica.com>,
"'<kerberos@mit.edu>'" <Kerberos@mit.edu>
In-Reply-To: <7E270C3427928E499F189C5636C52CDC45C76C24@smtp_mail.bankofamerica.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On 01/05/2015 04:04 PM, Xie, Hugh wrote:
> Any follow up on this issue? Do you need any more information? Should I turn on debugger to see where this error occurred, if yes I need some pointer which files to set break points.
I'm a bit confused by the information given so far, and I think some of
my questions weren't clear enough. Let's start over.
For the non-working server only:
1. On the server, run "klist -k" (or "klist -k -t /path/to/keytab" if
the server is using a special keytab location). What is the output?
2. On the client, run kinit so that you have a fresh credential cache,
then try to connect. Then run klist. Other than
krbtgt/COMMON.BANKOFAMERICA.COM@COMMON.BANKOFAMERICA.COM, what service
principal appears in the output?
3. On the client, run "kvno SPRINC", where SPRINC is the answer to
question 2. What is the output?
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos