× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2014

Re: KRB5_CC_BADNAME on EIM

There was a recent thread about this - you have to let Active Directory know about your IBM i being a trusted server - something like that - for Windows file sharing.

Do a search in the lists for QNTC, recent posts. And maybe call IBM support - they should be able to help you get it set up.

This isn't really an EIM issue, as I recall - it is about forwarding tickets - I think that was in the latest thread.

HTH
Vern

On 4/17/2014 10:10 AM, Justin Taylor wrote:
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.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.