White Papers

114 Lifecycle Controller Integration Best Practices Guide

16 Role Based Authorization Profile (RBAP) use cases

16.1 Discovery of RBAP Profile Support

Use the following procedure below to confirm the existence of Role Based Authorization profile support.

Note: Prior to LC2.0.0, this profile resided as a CIM profile, not LC profile.

Applies to: LC1.5.0+

Prerequisites for script: none

Script: GetRBAProfile.win

A) The Lifecycle Controller remote service must be in a “ready” state before running any other WSMAN commands.

The GetRSStatus() method or the GetRemoteServicesAPIStatus() method may be used depending on the version of the

LC Management registered profile.

B) [LC1.5.0/LC1.5.1]GetCIMRegisteredProfiles():

[LC2.0.0]GetLCRegisteredProfiles():

ENUMERATE the applicable class to view all registered profiles. See section 2.2 for a ENUMERATE .

C) Search for “RegisteredName= Role Based Authorization” and note its instanceID to use in step D)

D) [LC1.5.0/LC1.5.1] GetCIMRegisteredProfile(): [LC2.0.0] GetLCRegisteredProfile():

GET the applicable instance using the InstanceID from C). See Section 2.3 for a definition of GET.

Results for the InstanceID of DCIM:RoleBasedAuthorization:1.0.0 shown below. If no instance is returned, the profile is

not supported.

DCIM_LCRegisteredProfile

AdvertiseTypeDescriptions = WS-Identify

AdvertiseTypeDescriptions = Interop Namespace

AdvertiseTypes = 1

InstanceID = DCIM:RoleBasedAuthorization:1.0.0

OtherRegisteredOrganization = DCIM

ProfileRequireLicense

ProfileRequireLicenseStatus