-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReflectionException (-1) "Class does not exist" #192
Comments
I'm getting the same error but your fix does not work for me. |
@lloydie-t : For me it also worked to just comment it out: // 'saml2_controller' => '', |
According to the readme you should be passing your controller's fully qualified namespace:
so, in my specific usecase, I had a controller file So my setting is: And it works perfectly. +1 to @xnasa for opening this, as the default beahvior of blank will cause this error out of the box. |
@xnasa I am using 'saml2_controller' => 'Aacotroneo\Saml2\Http\Controllers\Saml2Controller', but still getting same error.. |
Above issue has been fixed on server but still on my local system. getting new issue Route [saml_login] not defined. (View: C:\xampp\htdocs\cfxproduct\resources\views\auth\login.blade.php) |
i got Class saml does not exist it was because i forgot to add saml to the $middlewareGroups in Kernel.php |
laravel-saml2 : 2.0.0
Laravel 5.8
After initial install and config for the 'test' idp. I tried
http://127.0.0.1:8000/saml2/test/metadata
and received the error in the title.In the saml2_settings.php file the following is set as default
If you notice, and this took me a while to see it, there is an extra space in the error message.
I believe that the controller in the vendor files is not being used.
When I did this
'saml2_controller' => 'Aacotroneo\Saml2\Http\Controllers\Saml2Controller',
to explicitly use the vendor...src\ file then the route metatdata worked and produced metadata.So it appears that the default, as the config states, is not being used in replacing the empty config file string.
The text was updated successfully, but these errors were encountered: