Operations Manager workflows, such as rules, tasks, monitors, and discoveries, require credentials to run on a targeted agent or computer. By default, workflows use the default action account for the agent or computer. The credentials for the default action account are configured when Operations Manager is installed.
When a workflow requires credentials that the default action account cannot provide, the workflow can be written to use a Run As profile. A Run As profile can have multiple Run As accounts associated with it. The Run As accounts let you specify the necessary credentials for specific computers. Multiple workflows can use the same Run As profile. The following image illustrates the relationship between workflows, Run As profiles, and Run As accounts.
In the image, three workflows use the same Run As profile. The Run As profile has three associated Run As accounts. In this example, each workflow that uses the Run As profile will run on Computer A by using the credentials for Run As account 1, on Computer B and C by using the credentials for Run As account 2, and on Computer D by using the credentials for Run As account 3.
Run As accounts can target a class, group, or object. A Run As account can be one of the following types:
- Windows - Windows credentials, for
example, domain\user name, or user name@FullyQualifiedDomainName,
and the associated password
- Community String - SNMP version 2
community string
- Basic Authentication - standard basic
Web authentication
- Simple Authentication - any generic
user name and password combination, for example, web form, SQL
Server authentication, or anything else that accepts user name and
password
- Digest Authentication - standard
digest web authentication
- Binary Authentication - user-defined
authentication
- Action Account - Windows credentials
that can only be assigned to the action account profile
- SNMPv3 Account - user name, context,
authentication protocol, authentication key, privacy protocol, and
privacy key for an SNMP version 3 device