#220 Store all ccaches in mechglue as pointers into the keyring
Closed: Deferred 4 years ago by simo. Opened 6 years ago by rharwood.

Everything should be in a gssproxy specific keyring. Each user ccache is a pointer into the gssproxy specific one. The timeout is reduced (an hour?) so that repeated create-and-destroy doesn't cause them to pile up overmuch.

This will allow us to properly handle the multiple principal case in FILE ccaches combined with our flushing logic.


Project has moved please reopen here if still an issue:
https://github.com/gssapi/gssproxy/issues

Metadata Update from @simo:
- Issue close_status updated to: Deferred
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata