FortiGate 1 is the member I started from to make the policy package.
And all works fine, but when I try to deploy new policy there is an error in FortiManager on FortiGate 2 and 3:
Post vdom failed:
error :131 - datasrc invalid. object: user saml.ssl-azure-saml:idp-cert. detail: REMOTE_Cert_3. solution: data not exist
Post vdom failed:
error :131 - datasrc invalid. object: user saml.ssl-azure-saml:idp-cert. detail: Remote_Cert_4. solution: data not exist
It seems not to exist the Remote Certificate associated on SAML user account, but I see this certificate in FortiGate and in device DB on FortiManager.
Unfortunately I noticed that it is not possible to make a dynamic object for this Remote Certificate object.
I also noticed that the configuration of the SAML FortiGate 2 and 3 user was overwritten at the first synchronization of the policies. I had to reconfigure the relative settings from the FortiManager CLI to restore the authentication of the VPNSSL.
How should I manage the Remote Certificate and the SAML user configuration if I have a shared policy package within the same ADOM? What other actions can I take to investigate the problem further?
you can try to import the certificate by FortiManager CLI and give this a distinct name as in not REMOTE_CERT_1 or what the default is, but something like "SAML_Remote_Cert". Writing and overwriting even should work.
IF there is a problem finding that number _3 etc, check the command set on the FortiGate directly.
config user saml
set idp_cert ? (question mark to show what the available datasource entries are)
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.