Bug 991170

Description of problem:
In F18 (I think) the default cred. cache location changed, but this new location was put into KRB5CCNAME so that programs not updated to the new location would still function.

The setting of KRB5CCNAME was removed as per:

https://mail.gnome.org/archives/commits-list/2013-May/msg05519.html

However, java programs now use the wrong location (/tmp/krb5cc_uid).

Version-Release number of selected component (if applicable):
java version "1.7.0_25"
OpenJDK Runtime Environment (fedora-2.3.10.10.fc19-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

or 

gdm-3.8.3-2.fc19.x86_64

depending on your perspective.

How reproducible:
Always

Steps to Reproduce:
1.Use,e.g. SampleClient and SampleServer from JAAS 
2.
3.

Actual results:
Credential cache is not found at correct location.  Using "-Dsun.security.krb5.debug=true" one can see:

>>>KinitOptions cache name is /tmp/krb5cc_42001



Expected results:
Uses cache in the new "standard" location.

Additional info:
Sample programs available at:

http://docs.oracle.com/javase/7/docs/technotes/guides/security/jgss/tutorials/ClientServer.html

My JAAS config for client:
com.sun.security.jgss.initiate {
  com.sun.security.auth.module.Krb5LoginModule required 
    useTicketCache=true
    ;
};

My JAAS config for server;
com.sun.security.jgss.accept {
  com.sun.security.auth.module.Krb5LoginModule required 
    debug=true 
    storeKey=true 
    useKeyTab=true 
    keyTab="/path/to/krb5.keytab" 
    principal="myservice/host.example.com"
    doNotPrompt=true
    isInitiator=false;
};