No Provider Metadata Available - shibsp :: ConfigurationException

I recently upgraded Shibboleth from Shibboleth-sp-2.5.6.0-win64 to Shibboleth-sp-2.6.0.0-win64 and the Apache web server from 2.4.16 to 2.4.23.

Post update when I try to access my application, I get the following error:

shibsp::ConfigurationException The system encountered an error at Fri Oct 14 20:19:51 2016 To report this problem, please contact the site administrator at root@localhost. Please include the following message in any email: shibsp::ConfigurationException at (https://xxxxxx.xxxx/) No MetadataProvider available. 

When I access, https: /xxxxx.xxxxx/Shibboleth.sso/Metadata, the metadata file is loading and the details seem to be correct.

Does anyone know why this error occurs and how we can solve it?

+5
source share
2 answers

Make sure you have a default partition, as well as an override if one exists. For me, even though a section was created to override, it needed one of the default values

0
source
  • Go to shar.log, check what the object identifier returned from the IDP approval message means.
  • Go to the appropriate IDP metadata on the SP side, compare both object identifiers.
  • Of course, there must be some discrepancy between them, so the SP cannot find the IDP that he is talking to, and could not continue the flow. Update the object identifier in the IDP metadata and restart shibd. It should work.
0
source

Source: https://habr.com/ru/post/1258224/


All Articles