For those in the business of developing applications, this is the answer to a difficult problem. Now with the use of and combination of HTML, CGI, PERL and to a greater extent in time JAVA, the capability of delivering full fledge applications on the Web is possible. What is novel is that now our customers can join us in helping to deliver applications to their customers because of the greater availability of Web development tools and the ease in which the less complicated applications coupled with a relational data base can be written. It is to this fact that the customers are joining the central development teams which requires a standardized method of authentication. With such a standard, anyone developing a system in which authentication is required should be able to include a standardized interface which can provide authentication by using a central authentication server.
Ingenuity fills the void when procedures are unavailable.
For the sake of example, there have been two Web applications distributed to the campus which due to pressures of timing and the lack of a central approved method used creativity to provide authentication. Upon getting a valid signon to this server, a logout is made and then a logon to the appropriate server for the CAMS system is accomplished. CPPC takes another approach to security authentication. University id number. The major problem with this approach is that the use of FTP can be a problem in high volume usage and in the event the FTP process is down, so is this authentication process.