John Apple II

I've raised this bug in the Chromium project which is for the same issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1087704&q=&can=4

Also, note, that once I the codes hang on the key, I have to physically remove the key and reinsert it into a different slot, or the Authenticator app no...

I have just confirmed - unsetting the PIN on the key causes the error to no longer appear between the authenticator app and the Chrome/Chromium browsers, however, new keycodes will...

Chromium developers believe this is something to do with nss-kit and that both Chromium and the Authenticator app are accessing the user-specific/system-wide nss stores

Another update, something that may or may not be related, but when I use anything that requests FIDO/U2F auth from the key, the touch-based TOTP function on the key seems...

I note that this issue continues on Fedora 33 as well with Chromium, but with the latest Firefox only open, there is no conflict. It only occurs when Chromium is...

Examples of failures today: AAP2 Networking Automation Workshop [rh067f] AAP2 Networking Automation Workshop [rhd351] AAP2 Networking Automation Workshop [rha6c0] AAP2 Networking Automation Workshop [rh189f]

Hi, @cloin, I'm not sure how we're supposed to do this, as we use this repo directly and execute it via the RHPDS interface. @IPvSean @heatmiser - can you advise...

Hi, @IPvSean Looking into the GPE account, the grant for this item exists already for this item. We cannot tell why this is asking us to accept terms when we've...

So, we use a service account which has no console access in order to provision these labs - are we going to have to find a way to login to...