[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Pulp-list] Minor usability problem with stale cached login credentials



On 03/21/2012 11:46 PM, Nick Coghlan wrote:
After spending some time trying to figure out why my management client
was complaining that my server's SSL cert had expired (despite the fact
I had just regenerated the cert), I eventually realised it was actually
complaining about the locally cached cert that holds the server login
details.

Part of that's a display problem in my own management client [1], but
I'm considering raising an upstream bug on Pulp as well, since the error
details from Pulp in this case are currently just:

"sslv3 alert certificate expired"

Changing that to something like "Cached login credentials have expired,
please refresh with 'pulp-admin auth login'" would definitely have saved
me some time today.

Regards,
Nick.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=805763

This is one of those things that annoyed us in the beginning and after a while of never getting around to fixing it, we developed blinders and don't even notice anymore :)

This sprint I'm looking to get login/logout functionality into the v2 client, I'll make sure I don't fall into the same trap again.



--
Jay Dobies
Freenode: jdob @ #pulp
http://pulpproject.org | http://blog.pulpproject.org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]