Various requests have been made if gssproxy cannot refresh kerberos tickets in the background, so users do not need to run an external trigger for ticket refresh (run by cron, etc.).
This is implemented for (client-)keytab initiated credentials, tracking externally initiated credentials is very complex. We do not consider implementing it (yet). Closing as fixed.
Metadata Update from @gd: - Issue assigned to gd - Issue set to the milestone: 2013 May