Hi there,
There have been a few changes to systemd files recently so I wanted to check about how to correctly supply environment variables to the server. For example, KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs
On 13 Jun 2019, at 14:17, William Brown wbrown@suse.de wrote:
Hi there,
There have been a few changes to systemd files recently so I wanted to check about how to correctly supply environment variables to the server. For example, KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
ping .... anyone?
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs
On Thu, Jun 20, 2019 at 12:25 PM William Brown wbrown@suse.de wrote:
On 13 Jun 2019, at 14:17, William Brown wbrown@suse.de wrote:
Hi there,
There have been a few changes to systemd files recently so I wanted to check about how to correctly supply environment variables to the server. For example, KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
ping .... anyone?
Use a drop-in with Environment=? :) Don't know what the context is but for e.g. IPA they could ship /usr/lib/systemd/system/dirsrv@.service/ipa.conf in their packages, or the /etc/* equivalent if it is something more variable.
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org 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/389-devel@lists.fedoraproject....
On 20 Jun 2019, at 12:30, Matus Honek mhonek@redhat.com wrote:
On Thu, Jun 20, 2019 at 12:25 PM William Brown wbrown@suse.de wrote:
On 13 Jun 2019, at 14:17, William Brown wbrown@suse.de wrote:
Hi there,
There have been a few changes to systemd files recently so I wanted to check about how to correctly supply environment variables to the server. For example, KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
ping .... anyone?
Use a drop-in with Environment=? :) Don't know what the context is but for e.g. IPA they could ship /usr/lib/systemd/system/dirsrv@.service/ipa.conf in their packages, or the /etc/* equivalent if it is something more variable.
SUSE has a "supported" configuration where you use krb with 389, but the KDC is external, so we need to provide the ldap/hostname@ream keytab to the server for GSSAPI. I wanted to be sure that this was the way we were approaching the configuration now :)
So I think that the drop in with Environment= is correct here, and I should test it on suse some time. Thank you!
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org 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/389-devel@lists.fedoraproject....
-- Matúš Honěk Software Engineer Red Hat Czech _______________________________________________ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org 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/389-devel@lists.fedoraproject....
— Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server SUSE Labs
389-devel@lists.fedoraproject.org