It is important to consider the effect of these design options when implementing security during the development of a IBM Cúram Social Program Managementapplication. They are the first and last line of defense against unauthorized access to application process functionality. Generally speaking, security will be switched on for almost all process methods. Security may be switched off for a process method that does not need security, e.g., a login method that gets invoked when a user tries to login to an application. As a user has not yet been authenticated or authorized, they need access to this method in order to login, therefore switching off security for this method may be necessary.
During the initial design phase of an application the overhead of keeping the security environment "in sync" with an evolving application can be tedious. It is possible to disable the authorization check by setting the curam.security.disable.authorisation property in the Application.prx file.
The curam.security.disable.authorisation property should only be turned on at design phase. This should never be set to true in a production environment.
Finally, it should be noted that once the code and scripts have been generated from a working model, the information associated with a FID cannot be changed. To change this information requires modifying the model, re-generating and re-building the database.