Hide Forgot
Description of problem: I try to login to https://beta.bugzilla.redhat.com/bugzilla/ using 'Red Hat Associate' button or with password and both fail on: The IDP's reply failed validation: Crypt::OpenSSL::VerifyX509::verify: x509 is not of type Crypt::OpenSSL::X509 at /usr/share/perl5/vendor_perl/Net/SAML2/Binding/POST.pm line 67. .
Same here. Running Fedora 24 with the latest updates and using Google Chrome 55.0.2883.75 (64-bit)
Same here. When I try to manually enter @redhat.com address with password (rather than the Associate login button) I get a "url too long" error.
At the top of every page there is a big blue box, the second line in that box is: The Red Hat Associate (RHA) IDP is currently not functioning where "currently not functioning" is bold. We are waiting for the IDM team to reimport the metadata to fix this. FYI It's my fault, we had to change the URL path to avoid production cookies being sent to the beta sub domain, which broke SSO :-( We didn't have time to wait for it to be fixed due to time constraints.
(In reply to Richard Guy Briggs from comment #2) > Same here. When I try to manually enter @redhat.com address with password > (rather than the Associate login button) I get a "url too long" error. I wonder if part of the SSO data is still in the URL? Can you click the home link and then try to login?
(In reply to Jeff Fearn from comment #4) > (In reply to Richard Guy Briggs from comment #2) > > Same here. When I try to manually enter @redhat.com address with password > > (rather than the Associate login button) I get a "url too long" error. > > I wonder if part of the SSO data is still in the URL? Can you click the home > link and then try to login? Ok, starting from "beta.bugzilla.redhat.com", then clicking "home", "login", then "bugzilla account" with my account name and password did work this time.
Once logged in and looking at a valid bug (1379453), all the redhat icons next to account names obscure and overlap the end of the link text on smaller font sizes.
There is another Bug 1409653 for dirty URLs affecting logins, other than that SSO is working fine..