Hi.
I'm working on the integration of a zabbix server with a GLUU IDP server, I am following the recommendations of https://www.zabbix.com/documentation/current/manual/web_interface/frontend_sections/administration/authentication#saml_authentication. I am
first, I exposed the zabbix server on port 443 with their respective SSL certificates. This server run with CENTOS8

Then put the certificates in the recommended folder, including the idp.crt

This is the SAML configuration that I have in zabbix

and this is the metadata that you create to create the trust relationship with the IDP:

When I try to authenticate, I receive this message from apache

and I get several questions about the whole process:
1) the certificate that is saved in the path ui / conf / certs / idp.crt is the signing or the encryption?
2) Do you have any clues as to why this error occurs in apache?
3) is there an error in the SAML parameterization in zabbix?
Thanks in advance for any assistance.
I'm working on the integration of a zabbix server with a GLUU IDP server, I am following the recommendations of https://www.zabbix.com/documentation/current/manual/web_interface/frontend_sections/administration/authentication#saml_authentication. I am
first, I exposed the zabbix server on port 443 with their respective SSL certificates. This server run with CENTOS8
Then put the certificates in the recommended folder, including the idp.crt
This is the SAML configuration that I have in zabbix
and this is the metadata that you create to create the trust relationship with the IDP:
When I try to authenticate, I receive this message from apache
and I get several questions about the whole process:
1) the certificate that is saved in the path ui / conf / certs / idp.crt is the signing or the encryption?
2) Do you have any clues as to why this error occurs in apache?
3) is there an error in the SAML parameterization in zabbix?
Thanks in advance for any assistance.