Page History

...

1. Create a Model whose name matches the name of the Plugin. In this example, the Model is created at app/Plugin/MyPlugin/Model/MyPlugin.php.

2. Define $cmPluginType to indicate the type of the Plugin, from the following options:

   $cmPluginType	Description	Available Since	Instantiated?
   authenticator	Authenticator Plugin	v3.1.0	Yes
   cluster	Cluster Plugin	v3.3.0	Yes
   confirmer	Invitation Confirmer Plugin	v3.1.0	No
   dashboardwidget	Dashboard Widget Plugin	v3.2.0	Yes
   datafilter	Data Filter Plugin	v3.3.0	Yes
   enroller	Enrollment Flow Plugin	v0.9.4	Yes, as of v4.0.0
   identifiervalidator	Identifier Validation Plugin	v2.0.0	Optional
   job	Job Plugin	v3.3.0	Yes, when queued
   ldapschema	LDAP Schema Plugin	v2.0.0	Yes, via LDAP schema configuration
   normalizer	Normalization Plugin	v0.9.2	No
   orgidsource	Organizational Identity Sources Plugin	v2.0.0	Yes
   provisioner	Provisioning Plugin	v0.8	Yes
   other	Any other type of Plugin	v0.8	No

   As of v2.0.0, $cmPluginType may also be an array. A Plugin that implements more than one plugin type is referred to as a Polymorphic Plugin. Note that, due to naming conventions and other constraints, not all combinations of plugin types may currently be supported. These constraints will be removed over time as Plugin interfaces are updated.

Here's an example Model:

class LdapProvisioner extends AppModel {
  // Required by COmanage Plugins
  public $cmPluginType = "provisioner";
}

...