Closed Tcharl closed 3 years ago
Not really, as there's only one standard
In Order to provide identity As a client machine I can use kerberos SSO ticketing system
Orchestrator
NFS DNS
https://github.com/sridhav/docker/tree/master/docker-kerberos to adapt using #59
Literature: https://www.linuxtoday.com/blog/integrating-ldap-and-kerberos-part-one-kerberos.html https://web.mit.edu/kerberos/krb5-1.5/krb5-1.5.4/doc/krb5-admin/domain_005frealm.html https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/s1-nfs-security https://jpmens.net/kerberos/ https://jpmens.net/2012/06/29/dynamic-dns-updates-using-gss-tsig-and-kerberos/
https://github.com/criteo/kerberos-docker
Category:
53
Submitted for vote?
Not really, as there's only one standard
Advantages of the solution
In Order to provide identity As a client machine I can use kerberos SSO ticketing system
Target platform:
Orchestrator
Integration:
NFS DNS
Existing deployment
https://github.com/sridhav/docker/tree/master/docker-kerberos to adapt using #59
Literature: https://www.linuxtoday.com/blog/integrating-ldap-and-kerberos-part-one-kerberos.html https://web.mit.edu/kerberos/krb5-1.5/krb5-1.5.4/doc/krb5-admin/domain_005frealm.html https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/s1-nfs-security https://jpmens.net/kerberos/ https://jpmens.net/2012/06/29/dynamic-dns-updates-using-gss-tsig-and-kerberos/
https://github.com/criteo/kerberos-docker