External User Applications

When developing an application for an external user, the following must be implemented:

• An external user client application, i.e., a separate EAR file containing the web client application.
• A custom logon.jsp , where the external application must pass in a parameter user_type indicating an external user is logging in.
• A custom class that extends curam.util.security.PublicAccessUser, which requires implementing the curam.util.security.ExternalAccessSecurity interface, must be provided. This abstract class contains methods responsible for the authentication and authorization of an external user.

As well as there being internal and external user types. There can also be different types of external users. For example, there may be an external user of type 'PUBLIC' who could have limited access to an external application. There could be another external user of type 'PROVIDER' who is a registered external user. The ability to have different types of external users provides more flexibility within an external application, allowing finer grained control over authentication of the external user based on the external user type.