Skip to main content
stvnkem
New Member
January 28, 2026
Question

Issue when trying to connect Fortigate to ForticlientEMS; Connection status: FortiGate not authorize

  • January 28, 2026
  • 1 reply
  • 256 views

Hello,

 

May I have some help with connecting FGT to FEMS please?

FGT version is 7.4.x FEMS version is 7.4.5.

 

Error on FGT after accepting the cert: Connection status : FortiGate not authorized

I cannot find any pending request on the Forticlient EMS under: "Fabric & Connectors-> Fabric Devices"

 

What is missing? Thanks in advance!

 

Screeshot of the FGT and FEMS settings:

https://ibb.co/Gf3n4Lfg
https://ibb.co/PGNPFt0b
https://ibb.co/qYzvB8Q4

 

Debug on FGT:

FGT7 (global) # diagnose test application fcnacd 13

FGT7 (global) # diagnose debug application fcnacd -1
Debug messages will be on for 30 minutes.

FGT7 (global) # diagnose debug enable

FGT7 (global) # [ec_ez_worker_base_prep_resolver:379] Outgoing interface index 3 for 1 (EMS-1).
[ec_ez_worker_base_prep_resolver:390] intf name: port1
[ec_ez_worker_base_prep_ssl:429] verify peer method: 2, current ssl_cb: (nil), new ssl_cb: 0xa5e300
[ec_ems_context_submit_work:578] Call submitted successfully.
obj-id: 0, desc: REST API to get EMS Serial Number., entry: api/v1/system/serial_number.

[ec_ez_worker_process:376] Processing call for obj-id: 0, entry: "api/v1/system/serial_number"
[_update_obj_stats:341] Storing (0, EMS-1, 14)
[ec_ez_worker_process:434] Call completed with failure.
obj-id: 0, desc: "REST API to get EMS Serial Number.", entry: "api/v1/system/serial_number".
error info: Error (-1@__generic_process_result_ex:200). HTTP code 403.

[ec_ez_worker_base_prep_resolver:379] Outgoing interface index 3 for 1 (EMS-1).
[ec_ez_worker_base_prep_resolver:390] intf name: port1
[ec_ez_worker_base_prep_ssl:429] verify peer method: 4, current ssl_cb: (nil), new ssl_cb: 0xa5e160
[ec_ems_context_submit_work:578] Call submitted successfully.
obj-id: 0, desc: REST API to get EMS Serial Number., entry: api/v1/system/serial_number.

[__get_ec_fctems_certificate_info:429] ems cert ca_cn: DC = com, DC = stvnkem, DC = lan, CN = lan-AD-SASE-CAems1.lan.stvnkem.com

[__get_ec_fctems_certificate_info:430] ems cert fingerprint: D4:F7:EA:77:3E:DC:E3:99:67:7C:C1:86:F3:5C:0E:F3:CC:E2:93:82:C0:A3:AF:66:53:A8:DC:49:AA:25:6C:05:EF:A8:B6:8B:3E:3B:84:01:CD:51:5D:23:2F:64:1C:36:99:7F:C0:0C:A8:F9:43:E9:21:29:44:70:FE:29:54:1A

[__match_server_cert_key:490] verify_peer_method: 4

[__match_server_cert_key:509] ret=1

[ec_ez_worker_process:376] Processing call for obj-id: 0, entry: "api/v1/system/serial_number"
[_update_obj_stats:341] Storing (0, EMS-1, 14)
[ec_ez_worker_process:434] Call completed with failure.
obj-id: 0, desc: "REST API to get EMS Serial Number.", entry: "api/v1/system/serial_number".
error info: Error (-1@__generic_process_result_ex:200). HTTP code 403.

1 reply

tbarua
Staff
Staff
January 30, 2026

Hi @stvnkem, 

 

Can you please verify whether multitenancy is enabled in EMS in this case? If multitenancy is enabled, test by disabling it and attempting the integration between FortiGate and EMS again.

KB as a reference: 

https://community.fortinet.com/t5/FortiClient/Technical-Tip-FortiClient-EMS-with-Multitenancy-enabled/ta-p/193949

https://docs.fortinet.com/document/forticlient/7.4.0/ems-administration-guide/619834/enabling-and-configuring-multitenancy

Best regards,

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT