Kuali Financial System 1.0
The Kuali Financial System (KFS) team is working to create a robust financial system designed specifically for the needs of higher education institutions. It is being designed to be modular and flexible such that it will meet the needs of all Carnegie Class institutions. KFS 1.0 consists of the core modules which make up the foundation of this comprehensive application.
This initial release of the Kuali Financial System (KFS) is the first in a series of planned releases in an effort to provide a richly featured financial system for use by higher education institutions. The KFS will meet GASB and FASB standards, enable a strong control environment, and provide a complete financial system free of any software licensing fees.
KFS Release 1.0 contains:
- Chart of Accounts
- Financial Transactions
- General Ledger
- Kuali Nervous System (KNS) - a core technical module composed of reusable code components that provide common pieces of functionality.
- Kuali Enterprise Workflow (KEW) - a general-purpose electronic routing infrastructure or "workflow engine".
System Requirements
Full specifications for system requirements are available here:
Kuali Server Setup
Documentation
Release Notes
Technical Documentation
User Documentation (PDF)
See KFS Demonstration at kualitestdrive.org!
License Requirements
The Kuali Financial System Software is Licensed under the:
Educational Community License Version 1.0
Acknowledgements
A list of third-party contributions is available here:
Kuali Third-party Contributors
Security Considerations
The Kuali development team recognizes the importance of security. Solutions for authentication, authorization, and encrypting sensitive data have been provided. It will be up to each implementing institution to provide the necessary setup, configuration, and possibly alternative implementations for these important functions.
Backdoor Functionality: KFS 1.0 is delivered with a testing feature that allows users to enter the application via a "backdoor" in order to become different users in different roles. This allows individual users to test the application acting in various roles with varying permissions. In order to disable this feature for your production deployment, you must use a build.environment of "prd".
Central Authentication Service - The version of the Central Authentication Service (CAS) shipped with KFS 1.0 currently does not require passwords. Implementing institutions will need to configure CAS to require passwords in order to activate secure authentication to the application
Encryption Service - KFS 1.0 uses the Demonstration Encryption Framework to secure and encrypt sensitive data. Implementing institutions will need to decide whether to use the delivered encryption framework or another encryption framework of their choosing. A unique key will need to be established as well
User Service - KFS 1.0 is delivered with the Kuali User Service for looking up users and determining authentication credentials, workgroup membership, and authorization permissions. Implementing institutions may choose to plug the Kuali User Service into a centralized source for user data such as an LDAP directory or institutional user service. This is the preferred approach. Otherwise, user data can be created and maintained within KFS as a stand-alone application. In addition, unique key stores must be established to support the encryption framework protecting user identifiable data.
Web Service - KFS 1.0 utilized Kuali Enterprise Workflow (KEW) for the routing and approval of financial transaction documents and for managing workgroup memberships. Communications between KFS and KEW happen via Web Services and XML. A unique set of key stores must be established for KEW in order to support the encryption framework protecting document data being processed by the workflow engine.
I accept the license requirements and have read the Security Considerations