Hello I encountered the same problem, and in fact using tshark, I discovered it was a certificate problem when trying to fetch the metadata URL through https Alert (Level: Fatal, Description: Certificate Unknown) My chain was not good on that server and confirmed using openssl s_client
Le jeudi 6 juillet 2017 12:59:00 UTC+2, Daniel Stahlnecker II a écrit : > > Hello, > Have you been able to solve this issue? I am running into the same error > and would be interested to know the solution if you where able to find one. > Thank you > > On Monday, May 29, 2017 at 3:08:54 PM UTC+8, Emilian Mitocariu wrote: >> >> Hi, >> >> I have a CAS 5.0.5 server (with ldap backend) and a Nextcloud server >> which i am trying to make it authenticate users with the CAS server using >> SAML2. When i go to Nextcloud, it redirects me to CAS but instead of the >> login page i get this message "Error: Metadata resolver could not be >> located from metadata". I attached a file with the logs. >> >> Anyone know how i could fix this? >> Thanks >> > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/4668aef9-6fc6-4848-871c-ceb82a144fff%40apereo.org.
