User Config is a means of dynamically providing configuration for users of Caplin’s client applications. It allows you to enable, disable, and configure application features for users of different types, with a simplified API and enhanced granularity over older permissioning systems, such as Liberator’s Permissioning Auth Module.
User Config is implemented by creating a Configuration Service in an adapter. A Configuration Service is a collection of Config Providers organised by asset class and user type, registered with Config Adapters. Config Providers provide User Config objects to be streamed to a number of StreamLink subjects, organised by the same criteria.
See User Config Adapters for a reference to the Config Adapters and their related objects in the FX Integration API.
For instructions on how to implement User Config, see Implementing User Config.
Relationship to Liberator auth modules
User Config removes a client application’s dependency on Liberator’s Permissioning Auth Module to supply user application-entitlements, but it does not remove the requirement for a Liberator auth module.
Users continue to require permission to subscribe to specific subjects. This is now delegated to tokenauth using the TokenPermissioning blade, that will enable the configuration subjects as part of the SSO (Single Sign-On) mechanism.
Disabling a feature in User Config does not prevent Liberator from accepting a user’s requests to StreamLink subjects related to that feature. It is the adapter’s responsibility to verify the user’s feature permissions.