confusa

The all-mighty Confusa v1.0

• Refactor CA/certificate handling

- Join process_csr and download_cert, create a single, consistent view.
- Move all cert and CSR functionality into the CA interface (the CA is after all the authoritative source wrt certificates).
- make tidy UML diagram
- Create a 'Certficate' model class, with all certificate-related operations. That can be stateful and reflect the full transition of a cert request to a full certificate.
- The abstract CA class should export only very basic, atomic abstract operations. Like: sign, status, retrieve, revoke, list. That should map well to the REST-API.
- The standalone-CA will probably continue to not receive an awful lot of attention. However, it will be kept throughout the remodeling process to ensure that our design is sufficiently generic so we can replace the Comodo-CA quite well with the current interface, should we ever need to.

• RI

- Support batch-generation (api, dtd etc)

• UI-workover

- Initially show only "My certificates" to the user
- The view should have two large buttons, "Request new" and "Revoke all" on top
- Upon pressing those buttons, the current views for processing CSR and revoking certs are shown

• Improve javascript behavior, look into jQuery.

• Download/staging-area for jGridStart and other OAuth clients.

It should be a section called "3rd party tools" or some such, as it is not tools developed by the Confusa team

No animals were harmed in the making of this milestone. New users
are encouraged to create their own milestones under supervision of
experienced project managers only.

This Milestone is provided "as is" and any expressed or implied
warranties, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose are disclaimed.

In no event shall the regents or contributors be liable for any direct,
indirect, incidental, special, exemplary, or consequential damages
(including, but not limited to, procurement of substitute goods or
services; loss of use, data, or profits; or business; interruption).

YAMBNRAM
('yet another milestone but not really a milestone', aka
'Not really a milestone, but a 'token' for discussing new tickets')

Tickets added here should be discussed, or at least reviewed by another member of the development team before assigning it to a milestone (and a developer).

Type of tickets:
- large changes
- change of general concept
- new features

Type of tickets not to add here:
- bugs
- cleanups
- you do the math.. :-)