1
edit
Changes
→Links
Together, these certs allow the builders to communicate with the koji hub and visa versa. After researching and a bit of tweaking, I managed to utilize a concept from Fedora Projects website (http://fedoraproject.org/wiki/Koji/ServerHowTo) and created a script which would make minimal effort for anyone making multiple certs, or for anyone who would rather quickly make a cert than learn the process.
In our scenario, we used SSL to perform our configuration, however, Kerboros has another means of accomplishing the same thing without requiring authentication. This path however is only a 'quick-fix' because eventually SSL will have to be used.
= Koji Cert Process=
# A certificate authority must be created.
# The certificate authority must have a private key and public key created
# A certificate must be created for the server using the configuration and signature of the ca
# Other clients can then be created such as the kojihub, kojiweb etc
= How to use the script=
Another issue I came across was the fact that different sources provided different "requirements". For example, some sources stated that when creating the kojihub and kojiweb certs that the "Common Name" value is required to be a FQDN (Fully Qualified Domain Name) while others said it didnt. This made troubleshooting the kojihub process rather strenuous.
= Acknowledgements=
[[User:Paul.W]]
[[User:Chris_Tyler]]
= Logos =
* Fedora
* Seneca
* Apache
* OpenSSL
= Links=
My Blog: http://sidsbr.blogspot.com/
Fedora Projects Koji Setup Document: http://fedoraproject.org/wiki/Koji/ServerHowTo
= Sources=
