Triplesec Codebase Intellectual Property (IP) Clearance Status
Description
Triplesec is a set of modules that enable the use of ApacheDS as an Identity Management solution. Triplesec includes the following items:
- Custom authorization schema for LDAP
- Authorization API for accessing policy information within the directory
- A Swing based GUI for configuring and managing authz and authn policy
- ApacheDS integration with Jetty/Tomcat for administrative interfaces
- Kerberos SAM module for 2-factor Authentication
- Administration API
- Custom ApacheDS Interceptor for managing referencial integrity
- Installer Configurations
- Utilities for 2-factor Authentication Client
- Demo web applications for using Triplesec
Project info
- The Directory PMC will be responsible for the code.
- Since Triplesec is really the embelishment of ApacheDS for a specific function it will become a subproject of the Apache Directory TLP.
- Officer or member managing donation: Alex Karasulu
Identify the codebase
| date | item |
|---|---|
| 2006-10-18 | If applicable, make sure that any associated name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product. |
SHA1 sum for donated software: 17b4b6e698a01a551d48d84b3d99cc63d357ee93 (1.0)
Copyright
| date | item |
|---|---|
| 2006-10-18 | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. |
| 2006-10-18 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. |
Identify name recorded for software grant: Alex Karasulu
Verify distribution rights
Corporations and individuals holding existing distribution rights:
- For individuals, use the name as recorded on the committers page
| date | item |
|---|---|
| 2006-10-18 | Check that all active committers have a signed CLA on record: erodriguez, akarasulu, ersiner, elecharny, tbennett, trustin |
| 2006-10-18 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA. |
| 2006-10-18 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. |
| 2006-10-18 | Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. |
Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
Organizational acceptance of responsibility for the project
Related VOTEs:
- http://www.archivum.info/dev@directory.apache.org/2006-10/msg00017.html