Supertype: AbstractSecurityProfileType

What function libraries and their functions can be called?

Item Summary
Name	Type	Multiplicity	Description
identifier	property string	[1,1]	Profile identifier.
description	property string	[0,1]	Free-form description (comment).
documentation	property string	[0,1]	Technical documentation for a particular object or construct.
decision	property AuthorizationDecisionType	[1,1]	Default decision for the profile.
library	container FunctionLibraryProfileType	[0,-1]	Profiles regarding individual libraries.

Items
- identifier
  
  Flags: RAM,runtime
  
  Multiplicity: [1,1]
  
  Profile identifier. Usually short string, essentially a simple profile name. Custom profiles should consider using URIs instead of simple names to avoid conflicts with built-in profiles that may be provided in later versions.
- description
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Free-form description (comment).
- documentation
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Technical documentation for a particular object or construct.
  
  The purpose of this element is to document system configuration and behavior. The documentation will not be presented to end users. In fact, it will probably not be presented at all in midPoint user interface. This documentation element is supposed to be a part of the technical documentation of midPoint deployment. The tools than generate deployment configuration will look for these elements and combine them to compiled documentation document.
  
  AsciiDoc formatting is assumed for this element. Any leading or trailing whitespace is skipped. Indentation equivalent to he indentation of the first non-blank line of text is also skipped.
- decision
  
  Flags: RAM,runtime,AVals:2
  
  Multiplicity: [1,1]
  
  Default decision for the profile. I.e. decision of those aspects of the profile that are not explicitly enumerated.
- library
  
  Flags: RAM,runtime
  
  Multiplicity: [0,-1]
  
  Profiles regarding individual libraries.