...
This software is subject to a 3-Clause BSD License as further seen in LICENSE file.
SPARC Technical Criteria
System Authentication
Requirements when using enterprise credentials to log in:
Supports Shibboleth with SAML 2.0
eppn is currently configured as the primary authentication attributes. Other attributes like cn, surname, and email are also required.
Web application where DUO would have to be managed by another application/configuration. It only interacts with Shibboleth through modified header information.
Local access can be turned on/off via configuration.
APIs
API token generation for external applications to connect with SPARC is currently only utilized for communication with SPARC’s partner application, SPARCFulfillment.
Uses a secure token authentication mechanism.
Potential utilization by other applications is possible; however, documentation resides with those applications.
Enterprise Data Platform/Operational Data Store
Requirements when data is included into external, enterprise-wide data platforms for reporting and analysis:
Full data model/data dictionary documentation does not currently exist. However, documentation for data attributes can be retrieved using command line tools.
Only data within SPARCRequest can be deleted, which has a recorded, audit log of all changes (e.g., when, what, who).
Bulk data changes do not occur automatically. Some changes can be manually run as necessary only by an administrator via command line.
Enterprise Data Network Connectivity
Ruby on Rails application. As such, it runs using Phusion Passenger and Apache.
Sole Network requirements include access to its underlying MySQL database (can be hosted with application or separately), access to the outside network via SSL to serve the application to the public. It can be kept within the DMZ for internal network use only or firewall rules can be put in place to allow external network use.