On Thu, 1 Aug 2019 at 03:52, Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
Stephen John Smoogen wrote:
>authentication methods require a lot of dedicated work because it affects
>all workflows somewhere.. and because it would mean so much downtime.. it
>has never gotten the resources in time and engineers to do.
Obviously replacing an authentication protocol is a big change that
affects many things, but some smaller improvements could make the user
interface suck less. Asking for a password instead of just failing is
an isolated client-side change. It would take some programming work of
course, but little or no coordination between different components.
I think we are talking about different things. I am talking about fixing
the backend to make it so fedpkg can authenticate easier. You are talking
about having fedpkg talk to a non-working 80% api backend. The fedpkg could
ask for a password.. it could also fail regularly spectacularly because the
backend wasn't meant to deal with that but was hacked together to sort of
work like that. So to make the front end have a better user experience..
you need to make the backend work consistently. [Even the kerberos side you
mention is not really tied into authentication easily.. but is done through
a set of clever programming to make disparate tools work together.]
Authenticating in advance with kinit would continue to work, so
workflow would break.
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Stephen J Smoogen.