SecureReference
Applies To: System Center 2012 - Operations Manager, System Center 2012 R2 Operations Manager, System Center 2012 SP1 - Operations Manager
Represents as secure reference type or a RunAs profile.
Schema Hierarchy
ManagementPack
TypeDefinitions
SecureReferences
SecureReference
Syntax
<SecureReference ID="Company.Product.SecureReferenceID" Comment=”Comment” Accessibility="Public/Internal" Context="TargetClassType"/>
Attributes and Elements
The following sections describe attributes, child elements, and the parent element of the SecureReference element.
Attributes
| Attribute | Description |
|---|---|
ID |
Required attribute. Represents the identity of the element. To learn how to identify your element in a management pack, see Element Identity and Namespace Conventions. |
Comment |
Optional attribute. Represents commentary by the management pack author. |
Accessibility |
Required attribute. Defines the visibility of the secure reference type. |
Context |
Required attribute. Represents the ID of the class type against which the secure reference is targeted. |
Accessibility Attribute
| Value | Description |
|---|---|
Public |
Indicates that this secure reference type is visible to external management packs for targeting or inheritance. In most cases, the Accessibility attribute should be set to Public so that the secure reference type can be reused elsewhere. |
Internal |
Indicates that external management packs cannot reference this secure reference type. |
Child Elements
None.
Parent Elements
| Element | Description |
|---|---|
Contains secure reference type definitions or RunAs profiles in a management pack. |
Remarks
Typically, workflow modules run using the default agent action account. However, to accommodate the case where the default agent action account does have the correct credentials to run a module in the workflow, the management pack author can define a SecureReference element within the management pack. It is up to the user to define the accounts to associate with the secure reference after the management pack is imported. If the user does not define the accounts to associate with the secure reference, the workflow modules will run, but they will run under the default agent action account, which might not be desirable.
Note
A display string for each secure reference type should be defined in the display string section of the management pack for at least one language. For more information, see DisplayStrings.
Example
The following sample shows how to define a SecureReference element in a management pack. Because the Context attribute is defined as the base class type for all class types, the secure reference can be applied to any workflow module in the system.
<SecureReference ID="Mom.Sample.SampleOperatorAccount" Accessibility="Public" Context="System!System.Entity"/>
The following sample shows how the preceding SecureReference element can be referenced in a workflow module. The ID of the SecureReference element is assigned to a WriteAction module’s RunAs attribute.
<WriteAction ID="Probe" RunAs="Mom.Sample.SampleOperatorAccount" TypeID="System!System.CommandExecuter">