-
Notifications
You must be signed in to change notification settings - Fork 42
Overriding authentication type per service
Each plugin which contains services has a corresponding folder within deploy where user settings and server settings can be stored.
The configuration needed is stored in "_internal" in the configuration dataservice storage
The reserved name folder "_internal" can exist within deploy/<scope>/<product name>/pluginStorage/<plugin ID>
Within _internal/services/<service name>
a file, authentication.json can exist.
This file can specify details about the authentication it requires, such as host & port of authentication server, but that information is custom to the authentication type.
The common attributes of authentication.json are:
enabled: true/false meaning whether any authentication is needed for the service. If false, authentication will be bypassed.
authType: is a string requesting a category of authentication, such as LDAP, rather than an implementation.
If no authType is given but enabled=true, the server will use the server's default authentication for that service.
{
"enabled": true,
"authType": "fallback" //where fallback is specified in the server's configuration JSON
}