-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
SAML enabled not reflected in GUI or endpoint /saml/acs but in database yes #9317
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
I'm seeing the same thing with my environment. I'm running in docker with v5.1.4 - build 5886. I was able fix the web gui not updating after a save buy following domunus's comment. I do get the same
error in my debug console along with the 403 page when trying to login with SAML. |
I have the same here with SAML also v5.1.4 - build 5886 on Ubuntu. 403 page when trying to login with SAML. |
What's the output of your logs? We have debug info that echoes out to the logs |
[2021-03-17 12:36:34] production.ERROR: RecursiveDirectoryIterator::__construct(/var/www/html/snipe-it/storage/framework/cache): failed to open dir: Permission denied {"exception":"[object] (UnexpectedValueException(code: 0): RecursiveDirectoryIterator::__construct(/var/www/html/snipe-it/storage/framework/cache): failed to open dir: Permission denied at /var/www/html/snipe-it/vendor/symfony/finder/Iterator/RecursiveDirectoryIterator.php:48) [2021-03-17 12:36:34] production.ERROR: UnexpectedValueException: RecursiveDirectoryIterator::__construct(/var/www/html/snipe-it/storage/framework/cache): failed to open dir: Permission denied in /var/www/html/snipe-it/vendor/symfony/finder/Iterator/RecursiveDirectoryIterator.php:48#56 /var/www/html/snipe-it/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(63): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}(Object(Illuminate\Http\Request)) Next Illuminate\View\ViewException: Route [account.accept] not defined. (View: /var/www/html/snipe-it/resources/views/layouts/default.blade.php) (View: /var/www/html/snipe-it/resources/views/layouts/default.blade.php) in /var/www/html/snipe-it/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php:420 |
Clearly there are some folder permission conflicts. |
@john57165 @BrettTactus @snipe any resolution found? |
Solved by referring to this thread. |
Expected Behavior (or desired behavior if a feature request)
SAML configuration settings to stick in the GUI after saving changes and SAML to work.
Actual Behavior
Upon saving SAML configuration using admin account the GUI alerts 'settings saved successfully'.
I check the database SAML fields to see the change was written and it was.
With debugging active, I navigate to https://assets.example.com/saml/acs and it responses with 403 Forbidden. The debugger shows ' SAML not enabled'.
Please confirm you have done the following before posting your bug report:
Provide answers to these questions:
After upgrading to V5.1.3
v5.1.3
PHP Version 7.2.24-0ubuntu0.18.04.6
mysql Ver 14.14 Distrib 5.7.31, for Linux (x86_64) using EditLine wrapper
Ubuntu 18.4.05 LTS and Apache 2.4.29 (Ubuntu)
Git
SAML not enabled. /var/www/html/snipe-it/app/Services/Saml.php#321
storage/logs
and your webserver's logs.Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
https://snipe-it.readme.io/docs/getting-help
The text was updated successfully, but these errors were encountered: