- Products
- Learn
- Local User Groups
- Partners
- More
Policy Insights and Policy Auditor in Action
19 November @ 5pm CET / 11am ET
Access Control and Threat Prevention Best Practices
Watch HereOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi,
I am trying to understand the requirements on the user account in order to connect to the web api without the need to be root.
Running "mgmt_cli login" with an admin user on an R80.20 management server triggers the error err_login_failed (message: Authentication to server failed).
No error is triggered if we use "mgmt_cli -r true" but we want to use session id and avoid logging in as root.
Attached are screenshots showing :
- [api status] the api is up with all access granted
- [user profile] the user (admin) has the "Management API Login" enabled
- [mgmt_cli login outputs] successful when run as root but failing when not using "-r true"
The same admin user account works fine to ssh to the management server or log into SmartDashboard.
Is there any requirement on the authentication method (we use "Checkpoint Password" here) to access the API without the need to be root (-r true)?
Thanks for any hint!
Our customer responded and it turns out the issue was due to confusion with regards to "Checkpoint authentication" versus "OS authentication" when attempting to use mgmt_cli
They had 2 user accounts with the same name:
Each with a different password.
When invoking "mgmt_cli login", they were using the password of the account created in the clish instead of the SmartConsole account.
It took us a while to figure it out but were able to reproduce.
Thanks for hinting the issue was related to the password.
I asked the customer to check his password for special characters and will update the post as soon as I hear back.
Thank you for the suggestion.
Our customer responded and it turns out the issue was due to confusion with regards to "Checkpoint authentication" versus "OS authentication" when attempting to use mgmt_cli
They had 2 user accounts with the same name:
Each with a different password.
When invoking "mgmt_cli login", they were using the password of the account created in the clish instead of the SmartConsole account.
It took us a while to figure it out but were able to reproduce.
Thanks for hinting the issue was related to the password.
Hi all,
In my case this does not resolve my issue of:
Trying to use the API from the ssh bash:
Situation:
[Expert@MDS:0]# api status
API Settings:
---------------------
Accessibility: Require all granted
Automatic Start: Enabled
Processes:
Name State PID More Information
-------------------------------------------------
API Started 14916
CPM Started 14916 Check Point Security Management Server is running and ready
FWM Started 15267
APACHE Started 13206
Port Details:
-------------------
JETTY Internal Port: 61236
JETTY Documentation Internal Port: 51238
APACHE Gaia Port: 4434 (a non-default port)
When running mgmt_cli commands add '--port 4434'
When using web-services, add port 4434 to the URL
Profile:
-------------------
Machine profile: 131072 or larger without SME - MDS
CPM heap size: 20480m
--------------------------------------------
Overall API Status: Started
--------------------------------------------
API readiness test SUCCESSFUL. The server is up and ready to receive connections
Notes:
------------
To collect troubleshooting data, please run 'api status -s <comment>'
What else does come to mind when thinking about this issue?
Best regards
Carsten
-r true logs in with a different user than admin (web_api, I think).
What is the precise error you get back?
What does $FWDIR/log/api.elg say?
Recommend engaging with the TAC also: https://help.checkpoint.com
Hi PhoneBoy
I get exactly the following
[Expert@MDSServer:0]# mgmt_cli login --port 4434 -d 5d6fd6s7-1235-a345-1234-s7d6s8d8f89d
Username: admin
Password:
code: "err_login_failed"
message: "Authentication to server failed."
[Expert@MDSServer:0]#
And the api.elg shows this, which I believe to belong together:
...
----------------------------
ID: 166785
Address: http://127.0.0.1:59929/web_api/login
Encoding: UTF-8
Http-Method: POST
Content-Type: application/json
Headers: {Accept=[text/plain], connection=[keep-alive], Content-Length=[95], content-type=[application/json], Host=[127.0.0.1:59929], User-Agent=[mgmt_cli], X-Forwarded-For=[127.0.0.1], X-Forwarded-Host=[127.0.0.1:4434], X-Forwarded-Host-Port=[443], X-Forwarded-Server=[10.1.2.3]}
--------------------------------------
2023-09-29 15:10:12,930 INFO com.checkpoint.management.web_api.web_services.WebApiEntryPoint.logRequestedCommandInfo:35 [qtp-1368107315-461921] - Executing [login] of version [1.8.1]
2023-09-29 15:10:13,521 ERROR com.checkpoint.management.web_api.utils.WebApiCommandExceptionUtils.getErrorReply:248 [qtp-1368107315-461921] -
com.checkpoint.management.coresvc.ngm_api.AuthenticationFailureLoginException: Authentication to server failed.
at com.checkpoint.management.dleserver.coresvc.internal.LoginSvcImpl.loginAuthenticationFailed(LoginSvcImpl.java:797)
at com.checkpoint.management.dleserver.coresvc.internal.LoginSvcImpl.authenticateUserByFwm(LoginSvcImpl.java:779)
at com.checkpoint.management.dleserver.coresvc.internal.LoginSvcImpl.performFWMAuthenticationRetry(LoginSvcImpl.java:1375)
at com.checkpoint.management.dleserver.coresvc.internal.LoginSvcImpl.access$7(LoginSvcImpl.java:3548)
at com.checkpoint.management.dleserver.coresvc.internal.LoginSvcImpl$FWMAuthenticationRetryRunnable.run(LoginSvcImpl.java:1)
at java.lang.Thread.run(Thread.java:820)
2023-09-29 15:10:13,522 INFO org.apache.cxf.interceptor.LoggingOutInterceptor.log:250 [qtp-1368107315-461921] - Outbound Message
---------------------------
ID: 166785
Response-Code: 400
Content-Type: text/plain
Headers: {Content-Type=[text/plain], Date=[Fri, 29 Sep 2023 13:10:13 GMT]}
Payload: code: "err_login_failed"
message: "Authentication to server failed."
--------------------------------------
[Expert@MDSServer:0]#
If this does not clarify (it doesn't to me), I'll have to go with the TAC.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 25 | |
| 15 | |
| 13 | |
| 10 | |
| 6 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Wed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchWed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY