Open main menu

CDOT Wiki β

Changes

Fedora-ARM,Dogfood - koji Hub

170 bytes removed, 17:02, 5 November 2010
no edit summary
Koji Authentication Selection
Koji primarily supports Kerberos and SSL Certificate authentication. For basic koji command line access, plain user/pass combinations are possible. However, kojiweb does '''not''' support plain user/pass authentication. Furthermore, once either Kerberos or SSL Certificate authentication is enabled so that kojiweb will work, the plain user/pass method will stop working entirely. As such plain user/pass authentication is a stop gap measure at best unless you intend to never setup a fully functional kojiweb instance. Deciding on how to authenticate users colors all the other actions you take in setting up koji so it's a decision best made up front.  For Kerberos authentication, a working Kerberos environment (the user is assumed to either already have this or know how to set it up themselves, instructions for it are not included here) and the Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.   
The Kerberos credentials of the initial admin user will be necessary to bootstrap the user database.
For SSL authentication, SSL certificates for the xmlrpc server, for the various koji components, and one for the admin user will need to be setup
[[Koji/ServerHowTo]]
== Project Plan ==
1
edit