KRB5_CC_BADNAME on EIM -- MIDRANGE-L

Subject: KRB5_CC_BADNAME on EIM
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Thu, 17 Apr 2014 10:10:46 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We're using IBM's Enterprise Identity Mapping (EIM) single-signon (SSO). I have one user who's getting a CPD3E3F (minor status code x'96C73A8B') when she tries to access QNTC via a PC5250 session. QSYSINC/H,KRB5 says that status code means KRB5_CC_BADNAME, but I'm not sure what to do with that info. The user connects to PC5250 with the SSO just fine, she just can't access QNTC. I've eliminated the PC as the problem because other users can access QNTC.

Anyone have any idea where I can go from here?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: KRB5_CC_BADNAME on EIM , Vernon Hamberg

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.