What is the architecture used by CAi?
CAi is a Java J2EE application running on Apache Webserver/Tomcat. CAi's data is stored in an Oracle database, which is backed up daily.
Is communication between our browser and the CAi secure?
Yes. All communication between CAi and your browser is performed using 128-bit encryption, making it virtually impossible for someone to intercept and decipher the contents of the communication.
What user ID/password mechanism is used by CAi?
CAi uses two levels of user ID and password authentication. The first account ID and password is the institution-level ID and password. After successful authentication of the institution ID and password, the user-level ID and password authentication is attempted. The institution ID and password are created and maintained by the NCAA. Each institution is in control of the user accounts able to access their data.
Can guest accounts be created with read-only access only? If so, can such accounts be turned on and off?
Each institution is in complete control of the accounts able to access their data, and the ability to create read-only accounts is implemented. Turning on and off accounts is also supported.
Can a user review successful and failed logins?
Currently, this feature is not implemented.
How is authentication and authorization handled for access to the database?
One database schema is used to connect to the database, and the connections to the database are pooled in the Web application to optimize performance.
Who can see my data?
Only users that are specified by your institution in the User Maintenance module of CAi can access your data.
© The National Collegiate Athletic Association