You can use Basic Authentication to identify users in the AirWatch architecture but this method offers no integration to existing corporate user accounts.

Pros

  • Can be used for any deployment method.
  • Requires no technical integration.
  • Requires no enterprise infrastructure.

Cons

  • Credentials only exist in AirWatch and do not necessarily match existing corporate credentials.
  • Offers no federated security or single sign-on.
  • AirWatch stores all user name and passwords.

Basic_Authentication

  1. Console user logs in to AirWatch SaaS using local AirWatch account for authentication (Basic Authentication)
    • Credentials are encrypted during transport
    • (for example, user name: jdoe@air-watch.com, password: abcd)
  2. Device user enrolls device using local AirWatch account (Basic Authentication) credentials
    • Credentials are encrypted during transport
    • (for example, user name: jdoe2, password 2557)