OpenWGA 7.6 - OpenWGA Concepts and Features

Installed plugins may be used as authentication sources. This is actually the same as using a Content store for authentication, only that this time it is no complete web app holding the user/group data but a plugin app and its content store. Authentication data like user and group definition documents are stored in the content store of the plugin and read from there to validate authentication requests.

Generally you need to prepare your plugin for being an authentication source just like a content store. See Structure of an authentication content store for details.

As a special step you need to declare the root documents for users and groups and all other settings via Integrated configuration. When using a plugin as authentication source there is no way to configure this settings, so the plugin itself needs to know its necessary settings.

Ensure the following settings in design configuration:

• In Tab "Plugin Configuration"
• Under "Usage" check the checkbox "Authentication Source"
• If your plugin has mixed usage and should also be available as web application (for example to provide managing access to defined users and groups) then you could now also change the "Authentication source" to "Myself", so the plugin web application uses itself as authentication source for web access.

Basically there is no need for special ACL settings for an authentication plugin. Especially it is not neccessary for the users of the authentication source to have any access to the authentication content store. But as you will need to provide any access to the data that your plugin holds you might also need to set the default access levels in tab "Design Configuration", so the plugin grants access without the ACL being modified.