-
Notifications
You must be signed in to change notification settings - Fork 24
GLPIv10 support? #132
Comments
Im currently developing against the latest glpi version and created a pull request to merge the latest changes in. |
If you cant wait: https://github.com/DonutsNL/phpsaml its not fully tested yet. |
It is actually working for version 1.20 if you put everything in the database manually. |
No manual insertion should be required, you should be able to install it and configure it using just the plugins config page. In my development environment (running the latest version of GLPI) it is functioning properly against Azure AD - SAML enterprise App. |
@DonutsNL can confirm that on GLPI 10.0.7 + latest master from https://github.com/DonutsNL/phpsaml results in empty page for /plugins/phpsaml/front/config.php Login does seem to work though even with modified #120 (comment) applied on top of https://github.com/DonutsNL/phpsaml (the file has changed to plugins/phpsaml/lib/php-saml/src/Saml2/Utils.php) Edit: https://glpi-project.org/glpi-9-5-x-will-be-discontinued/ is coming sooner than desired |
The error message is: |
I added type safety but was not yet able to test all possible conditions. As a work arround remove the type in de method listed. I.e requested_authn_context(string $var) to requested_authn_context($var) |
Thanks, @DonutsNL . Phpsaml expected 21 configuration items but got 19 items instead If I enable debug mode in GLPI, the additonal notice appears: |
Thats strange. It seems the db schema was not updated or the update was not called. Ill dive into that. See update.php what schema updates are required and run them manually. |
Thanks, @DonutsNL , for looking into it. |
Yea i prob did not update all versions yet and that also causes the update.php to not function. I was going to add a rerun option if less than expected items where found in the database. |
@DonutsNL one more addition regarding glpi 10 - this time about fusioninventory -> glpi inventory / glpi agent migration. Here's a patch for a couple-days-old phpsaml version, does not directly apply anymore but it should be easy to fix.
|
@AldarisPale This will help me and @derricksmith out keeping a good overview of issues and things. Thx |
@DonutsNL about #132 (comment) - when I downloaded bleeding edge from https://github.com/DonutsNL/phpsaml an upgrade was offered and plugin config page does not result in empty page anymore. Thanks! The current messages are: |
Thanks for checking and reporting back at me. This helps me greatly 👍 The messages shown are informational mostly and should allow you to check the sanity of the config a little better. To elaborate a bit more: No valid Ipd certificate details provided or available
The optional Service Provider Certificate is not configured, we strongly recommend that you do and enable strict mode
A different version of Phpsaml is marked as latest. Version 1.2.1 was found in the repository, you are running 1.2.2
I hope you like these additions, suggestions for additional validations are welcome ;-) |
Thanks, @DonutsNL So not clear why it is complaining, cannot see other error messages either. openssl php extension is installed |
you might be hitting a GLPI filtering issue I experienced whenever the first and initial update didnt go right and values are captured by the GLPI _POST handler. GLPI then replaces all line brakes with secure entities (to litteral \r\n) effectivly breaking the certificate. Breaking it because (if i remember correcly) X509 certificates only allows \n for a line breaks in base64 encoded certificates. I tried to correct the filtering issue post filtering with mixed results, i was considering the alternative capturing the $post in the acs.php before glpi would have a chance to filter stuff out. This might cause CSRF compliancy issues (as the CSRF field also being passed by the form). I was also considering an alternative like uploading the certificate file and storing it as CLOB or BLOB in the config field. |
validation as discussed in: derricksmith#132
This does not seem to support GLPIv10. Any chance we can get an update?
The text was updated successfully, but these errors were encountered: