[PATCH 4/6] Create the /api/ page providing the API token and information
bkabrda at redhat.com
Tue Jan 8 14:30:22 UTC 2013
----- Original Message -----
> On Tue, 8 Jan 2013, Bohuslav Kabrda wrote:
> > Yeah, CLI is on my TODO list :) But my plan was to utilize the
> > fedora
> > certificates, that are already used for e.g. koji builds. This way,
> > every user would be able to generate his certificate and most of
> > the
> > potential copr users (=packagers) already have that certificate. So
> > I
> > think it would be a more comfortable solution (although I haven't
> > discussed this possibility with anyone yet and I'm not even sure it
> > would be possible).
> >> Does this make sense ?
> I don't think we want to use the fedora koji certs. Multiple reasons:
> 1. it requires the user already be a packager - not just a fedora
> community member
> 2. it means we are tethered and dependent on koji
> 3. it overlaps the way the certs are used in a way that will be
> to users.
> A simple api key lets a cli exist and doesn't require that we
> implement or
> use a PKI.
I already accepted Pingou's patches, and they're deployed on the testing instance.
I still consider the certificates to be an interesting alternative authentication option. So if I ever decide to implement that, I will leave the api keys there.
Bohuslav "Slavek" Kabrda.
More information about the copr-devel