On Thu, Dec 15, 2022 at 10:42:28AM +0200, Alexander Bokovoy wrote: > >However, this would be approximately one billion times easier if I didn't > >need to worry about the hard part of automating something with fasjson, > >which is keeping a kerberos ticket fresh from a keytab. (I'd love to run my > >whole thing as a function-as-a-service function.) > > Why do you consider this as a 'hard thing'? > > If you are using GSSAPI, e.g. python-gssapi, you can rely on automated > ticket acquisition provided by the GSSAPI library from MIT Kerberos. > > export KRB5CCNAME=/path/to/ccache > export KRB5_CLIENT_KTNAME=/path/to/keytab > .. run your code .. > > That's all. Huh. All of the documentation I found suggested that there needed to be a sidecar container ... and a bunch of complication. For example: https://cloud.redhat.com/blog/kerberos-sidecar-container So, if I provide the keytab as a secret, set the above environment variables, and use requests-gssapi, it should just work? (And, does it matter where ccache points?) -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
