You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello david.
I have a problem with the configuration of glpi app.
i try to access to my glpi but i have serious problem?
My Glpi is configured with SSO authentification, my users are auto authetified with my DC.
so when i try to test my config i have a message to authenticate!
but it doesn't accept my login/password for glpi (my windows domain\user and password).
If i try browser access and not server(default) i have a message with cross!
and my httpd.conf
Can you help me?
Jérôme
Server GLPI Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-170-generic x86_64) 192.168.9.11
GLPI 9.4.4
Server Grafana (V6.5.1) CentOS8 192.168.9.14
The text was updated successfully, but these errors were encountered:
store updating angular $location.url /?orgId=1
2192.168.9.11/glpi/apirest.php/initSession:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
192.168.9.14/:1 Access to XMLHttpRequest at 'http://192.168.9.11/glpi/apirest.php/initSession' from origin 'http://192.168.9.14:3000' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Hello david.
I have a problem with the configuration of glpi app.
i try to access to my glpi but i have serious problem?
My Glpi is configured with SSO authentification, my users are auto authetified with my DC.
so when i try to test my config i have a message to authenticate!
but it doesn't accept my login/password for glpi (my windows domain\user and password).
If i try browser access and not server(default) i have a message with cross!
and my httpd.conf
Can you help me?
Jérôme
Server GLPI Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-170-generic x86_64) 192.168.9.11
GLPI 9.4.4
Server Grafana (V6.5.1) CentOS8 192.168.9.14
The text was updated successfully, but these errors were encountered: