The response was received at http://{GLPI}/marketplace/glpisaml/front/acs.php instead of https://{GLPI}/marketplace/glpisaml/front/acs.php about glpisaml

[DonutsNL]

This usually indicates that the response was proxied to the glpi webserver where the proxy connection to the webserver is not secured. This can only be fixed by securing the connection between the proxy and the backend. Alternatively (not adviced!) is to disable strict mode after which it will work but leaves your installation vulnerable. Rgdrs

[G0dzilla9]

Thanks for the reply !
Indeed when i disabled the stric mode it worked.
But i will try to put my glpi in https and then talk with my proxy in 443 instead of 80.
I will come back to update.

[jlucgauthier]

I don't know if you tried this, but you can use strict mode when REQUESTS PROXIED (in Transit) is enabled. It worked for us.

[G0dzilla9]

Ok, i tried but it doesn't work either. Could u give me both configurations on GLPI and ur Azure application ? thanks in advance !

[G0dzilla9]

Thanks for the reply ! Indeed when i disabled the stric mode it worked. But i will try to put my glpi in https and then talk with my proxy in 443 instead of 80. I will come back to update.

Update : I did change this and now my glpi talk with my opnsense in 443 but it still doesn't work...

[G0dzilla9]

Update and solved the issue : I only needed to add this line RequestHeader set X-Forwarded-Proto "https" to redirect in my file "glpi.conf" (on my glpi server) + activate the option "REQUESTS PROXIED" on the plugin (like said by @jlucgauthier).

Thanks !