It is possible that the Cúram JAAS login module may not support the authentication requirements for a particular custom solution. We strongly recommend that when developing a custom login module, that the Cúram JAAS login module be left in place and used with identity only authentication enabled. However, if deemed necessary, the Cúram JAAS login module can be removed and replaced by a custom solution. If this is the case Support must be consulted.
The Cúram JAAS login module adds new users to the Cúram Security Cache automatically, and when this Cúram JAAS login module is replaced by a custom JAAS login module, this functionality is no longer present. If a custom JAAS login module is completely replacing the Cúram JAAS login module, it is the responsibility of the custom JAAS login module to ensure an update of the Security Cache is triggered when a new user is added to the database.