You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 26, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,21 @@ ticket.updater_start()
17
17
18
18
If `keytab path` is not specifyed, kinit uses `KRB5_KTNAME` env, or `/etc/krb5.keytab` to find a keytab file. see: kerberos(1) and kinit(1).
19
19
20
+
### Ticket Updater Strategies
21
+
22
+
To avoid a credential cache (ccache) corruption by concurrent updates from multiple processes, KrbTicketUpdater has a few update strategies:
23
+
24
+
- SimpleKrbTicketUpdater: for single updater process, or multiple updaters w/ per process ccache. (default)
25
+
- MultiProcessKrbTicketUpdater: for multiple updater processes w/ exclusive file lock
26
+
- SingleProcessKrbTicketUpdater: for multiple updater processes w/ exclusive file lock to restrict the number of updater processes to one against the ccache
27
+
28
+
```
29
+
from krbticket import KrbTicket, SingleProcessKrbTicketUpdater
krbticket supports retry feature utilizing [retrying](https://github.com/rholder/retrying) which provides various retry strategy. To change the behavior, pass the options using `retry_options` of KrbConfig. The dafault values are:
0 commit comments