#11329 Unable to login with Fedora IDP in staging Bugzilla instance
Closed: Fixed by zlopez. Opened by mattia.

Based on previous replies to similar tickets, I'm raising the question here first... I'm unable to login into the staging instance of bugzilla at https://bugzilla.stage.redhat.com by using the Fedora IDP account.
The returned error is quite long:

Parsing of the IDP's metadata failed: no element found at line 1, column 0, byte -1: 94^ 521260337504 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187. at /usr/lib64/perl5/vendor_perl/XML/Parser/Expat.pm line 483. XML::Parser::Expat::parse(...) called at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187 eval {...} called at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 186 XML::Parser::parse(...) called at /usr/share/perl5/vendor_perl/XML/XPath/XMLParser.pm line 74 XML::XPath::XMLParser::parse(...) called at /usr/share/perl5/vendor_perl/XML/XPath.pm line 154 XML::XPath::find(...) called at /usr/share/perl5/vendor_perl/XML/XPath.pm line 176 XML::XPath::findnodes(...) called at /usr/share/perl5/vendor_perl/Net/SAML2/IdP.pm line 83 Net::SAML2::IdP::new_from_xml(...) called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Util.pm line 87 eval {...} called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Util.pm line 86 Bugzilla::Extension::SAML2Auth::Util::idp(...) called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Login.pm line 222 Bugzilla::Extension::SAML2Auth::Login::login_uri(...) called at /var/www/html/bugzilla/saml2_login.cgi line 18 ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_saml2_login_2ecgi::handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 ModPerl::RegistryCooker::run(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 173 ModPerl::RegistryCooker::default_handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 32 ModPerl::Registry::handler(...) called at /var/www/html/bugzilla/mod_perl.pl line 140 Bugzilla::ModPerl::ResponseHandler::handler(...) called at -e line 0 eval {...} called at -e line 0 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 192. XML::Parser::parse(...) called at /usr/share/perl5/vendor_perl/XML/XPath/XMLParser.pm line 74 XML::XPath::XMLParser::parse(...) called at /usr/share/perl5/vendor_perl/XML/XPath.pm line 154 XML::XPath::find(...) called at /usr/share/perl5/vendor_perl/XML/XPath.pm line 176 XML::XPath::findnodes(...) called at /usr/share/perl5/vendor_perl/Net/SAML2/IdP.pm line 83 Net::SAML2::IdP::new_from_xml(...) called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Util.pm line 87 eval {...} called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Util.pm line 86 Bugzilla::Extension::SAML2Auth::Util::idp(...) called at /loader/0x55f77c614a38/Bugzilla/Extension/SAML2Auth/Login.pm line 222 Bugzilla::Extension::SAML2Auth::Login::login_uri(...) called at /var/www/html/bugzilla/saml2_login.cgi line 18 ModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::var_www_html_bugzilla_saml2_login_2ecgi::handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 eval {...} called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 207 ModPerl::RegistryCooker::run(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 173 ModPerl::RegistryCooker::default_handler(...) called at /usr/lib64/perl5/vendor_perl/ModPerl/Registry.pm line 32 ModPerl::Registry::handler(...) called at /var/www/html/bugzilla/mod_perl.pl line 140 Bugzilla::ModPerl::ResponseHandler::handler(...) called at -e line 0 eval {...} called at -e line 0 . 

The prod instance works fine and they're both using the same Bugzilla 5.0.4.rh86 release.


Can you try again now?

Sometimes, and I have not been able to figure out why, the metadata file is 0 length / empty.

I ran the script to regenerate it and now:

-rw-r--r--. 1 ipsilon ipsilon 6862 May 21 16:25 /etc/ipsilon/root/saml2/metadata.xml

Thank you, now it works fine.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Issue status updated to: Open (was: Closed)

Metadata Update from @zlopez:
- Issue tagged with: low-gain, low-trouble, ops

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata