When two-factor authentication (2fa) is enabled on the KACE Systems Management Appliance (SMA), it may be noted that when attempting to connect to API, an error is received:
{"errorCode": -1, "errorDescription": "User not fully authenticated."}
For additional information, please refer to the API Reference Guide, which is located on the technical documents page for the SMA. For a full list of connection instructions and a walk-through example, please see Verifying API connection with Postman
Note: KACE Support is only able to assist with ensuring basic functionality of the API. For assistance with writing custom API, please contact Professional Services.
This is a fee-based service. Additional API related articles may be available in our knowledge base or on ITNinja.
For example, if the appliance name is KACE_SMA_Test, the route to supply the code can be: http://KACE_SMA_Test/ams/shared/api/security/verify_2factor.
The body for the POST request must contain the current code from 2fa.
{"currentCode": "codefrom2fa"}
If the code supplied by the authenticator was 123456, the following would be used:
{"currentCode": "123456"}
The header for this request should contain the following key:
Note: For 12.0 and later, "x-dell-api-version" and "x-dell-csrf-token" headers should be replaced with x-kace-api-version and x-kace-csrf-token respectively.
The value of the key above should have been obtained using unique user credentials in the steps already listed in the Authentication and organization selection section of the API Reference Guide. For a full list of connection instructions and a walk-through example, please see Verifying API connection with Postman.
Once a success is received, the custom API call should no longer return the error that the user is not fully authenticated.
{"Result": "Success"}
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center