AFSecurity.RemoveIdentity Method (PISystem, AFSecurityIdentity, IList(AFSecurity), Boolean)

public static void RemoveIdentity(
	PISystem system,
	AFSecurityIdentity identity,
	IList<AFSecurity> items,
	bool applyToChildren = false
)

Public Shared Sub RemoveIdentity ( 
	system As PISystem,
	identity As AFSecurityIdentity,
	items As IList(Of AFSecurity),
	Optional applyToChildren As Boolean = false
)

Dim system As PISystem
Dim identity As AFSecurityIdentity
Dim items As IList(Of AFSecurity)
Dim applyToChildren As Boolean

AFSecurity.RemoveIdentity(system, identity, 
	items, applyToChildren)

public:
static void RemoveIdentity(
	PISystem^ system, 
	AFSecurityIdentity^ identity, 
	IList<AFSecurity^>^ items, 
	bool applyToChildren = false
)

static member RemoveIdentity : 
        system : PISystem * 
        identity : AFSecurityIdentity * 
        items : IList<AFSecurity> * 
        ?applyToChildren : bool 
(* Defaults:
        let _applyToChildren = defaultArg applyToChildren false
*)
-> unit 

Parameters

system

Type: OSIsoft.AFPISystem
The PISystem containing the objects to be modified.

identity

Type: OSIsoft.AFAFSecurityIdentity
The AFSecurityIdentity to be removed from the objects.

items

Type: System.Collections.GenericIListAFSecurity
The list of AFSecurity objects to have the security rights modified for the user account.

applyToChildren (Optional)

Type: SystemBoolean

This parameter only has an effect if the associated object is an AFElement or AFEventFrame that has been added to a collection and saved to the server. For all other objects or if this parameter is , then the new access permissions are only applied to the associated object.

If and the associated object is an AFElement or AFEventFrame that has been added to a collection, then the access permissions for any parent or child objects might also change. The behavior depends on the reference type:

• For weak reference types, access permissions are never inherited. So, if you change the access permissions for the parent object, the permissions for the child object are not affected. Similarly, if you change the access permissions for the child object, the permissions for the parent object are not affected.
• For parent-child reference types, child permissions change when you change the permissions on the primary parent permissions. Parent permissions do not change when you change child permissions. Child elements that have a parent-child reference to the parent element, but are owned by a different element, are not in the primary path and will not have their permissions modified.

If the AFElement or AFEventFrame is a new object that has not been saved to the server, then it will be automatically saved so that the server can apply the security changes to the children.

Notes to Callers

For composition reference types, access permissions for child and parent are always the same, therefore the value of this parameter is ignored. So, if you change the access permissions for the child, the parent access permissions are automatically changed to match the child permissions. Similarly, if you change the access permissions for the parent, the child access permissions are automatically changed to match the parent permissions. These changes cascade down (and up) through the hierarchy.

AFSDK

Reference