Auth Problems with REST API since Update to FortiOS 7.4.5 Build 2702

[Matthias_Kirchhoff]

Hi there,

we manage our guest-wifi via REST-API from our intranet. Everything worked fine since we updated the Fortigate to FortiOS 7.4.5. Now we get an error "[httpsd 10151 - 1727870754     info] api_access_check_for_api_key[657] -- Wrong vdom." 

I was not able to find any REST-API documentation for this version to adapt my scripts. 

We communicate via cURL to the Fortigate.

Is there someone who can assist me with a REST-API documentation for this version?

Here are the informations from the debug-log:

here is the info from the debug-log:

\[httpsd 10151 - 1727870754     info\] api_access_check_for_api_key[657] -- Wrong vdom.
[httpsd 10151 - 1727870754  warning] _lock_out_check_and_lock_out[416] -- Failed api-key login attempt from xxx.xxx.xxx.xxx. (1/3 attempts within 120s).
[httpsd 10151 - 1727870754     info] fweb_debug_final[355] -- Completed GET request for "/api/v2/cmdb/wireless-controller/wtp/" (HTTP 403 Forbidden)
[httpsd 10149 - 1727870754     info] fweb_debug_init[531] -- New GET request for "/api/v2/cmdb/user/group/WiFi-xxxxxxxx/" from "xxx.xxx.xxx.xxx:52146"
[httpsd 10149 - 1727870754     info] fweb_debug_init[533] -- User-Agent: "(null)"
[httpsd 10149 - 1727870754     info] fweb_debug_init[535] -- Handler "api_cmdb_v2-handler" assigned to request
[httpsd 10149 - 1727870754     info] api_access_check_for_api_key[657] -- Wrong vdom.
[httpsd 10149 - 1727870754  warning] _lock_out_check_and_lock_out[416] -- Failed api-key login attempt from xxx.xxx.xxx.xxx. (2/3 attempts within 120s).
[httpsd 10149 - 1727870754     info] fweb_debug_final[355] -- Completed GET request for "/api/v2/cmdb/user/group/WiFi-xxxxxxxx/" (HTTP 403 Forbidden)

Waiting for answers

Matthias Kirchhoff

[saleha]

Hello,

Thank you for reaching out. I found a possible match with an internal dev team open project where they are currently working on testing a possible fix to be added in future release. I recommend creating a support ticket on forticare for proper followup. Mainly the following debugs would be required to investigate:

diagnose debug application httpsd -1

diagnose debug application nodejs -1

diagnose debug enable 

Thank you,

saleha

[Matthias_Kirchhoff]

Hallo saleha,

here is the info from the debug-log:

\[httpsd 10151 - 1727870754     info\] api_access_check_for_api_key[657] -- Wrong vdom.
[httpsd 10151 - 1727870754  warning] _lock_out_check_and_lock_out[416] -- Failed api-key login attempt from xxx.xxx.xxx.xxx. (1/3 attempts within 120s).
[httpsd 10151 - 1727870754     info] fweb_debug_final[355] -- Completed GET request for "/api/v2/cmdb/wireless-controller/wtp/" (HTTP 403 Forbidden)
[httpsd 10149 - 1727870754     info] fweb_debug_init[531] -- New GET request for "/api/v2/cmdb/user/group/WiFi-xxxxxxxx/" from "xxx.xxx.xxx.xxx:52146"
[httpsd 10149 - 1727870754     info] fweb_debug_init[533] -- User-Agent: "(null)"
[httpsd 10149 - 1727870754     info] fweb_debug_init[535] -- Handler "api_cmdb_v2-handler" assigned to request
[httpsd 10149 - 1727870754     info] api_access_check_for_api_key[657] -- Wrong vdom.
[httpsd 10149 - 1727870754  warning] _lock_out_check_and_lock_out[416] -- Failed api-key login attempt from xxx.xxx.xxx.xxx. (2/3 attempts within 120s).
[httpsd 10149 - 1727870754     info] fweb_debug_final[355] -- Completed GET request for "/api/v2/cmdb/user/group/WiFi-xxxxxxxx/" (HTTP 403 Forbidden)

[lpizziniaco]

Hello Matthias,

Please to check that if you are using trusted hosts, they are set in the admin and the API User. Would you also please to regenerate the API key and try again? 

Thank you 
Regards 
Luca