App Control: Why does the DASCLI password sometimes get rejected?
search cancel

App Control: Why does the DASCLI password sometimes get rejected?

book

Article ID: 288970

calendar_today

Updated On:

Products

Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

We sometimes see when entering in the DASCLI or B9CLI password via the CLI, that we get an "Authentication Failed" message. When we attempt the login again, we are able to authenticate. Why does this happen?

Environment

  • App Control¬†Agent: All¬†Versions
  • Windows
  • MacOS
  • Linux

Resolution

CLI authentication won't work until the Config List file is loaded which can take a little bit depending on how many rules/approvals you have. The system is designed to default to blocking and locking a user before the dascli or b9cli can process a password command for security measures. This issue is not a defect, but by design.

Additional Information

To help avoid this issue, you should run either "DASCLI STATUS" for Windows agents, or "./b9cli --status" for Mac/Linux. Check to make sure the Config List is is current and shows 100%. The password then should be able to be authenticated.