Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Work Areas
Revision as of 21:03, 3 September 2006 by Unnamed Poltroon (Talk)
This page describes work areas of two kinds. Work concentrated on a particular code component. And work projects that cut across multiple components.
End-User installed components
- HBX - Higgins extension for Firefox
- Relying Party Policy/Tags
Developer clients
- Demo app - Eclipse RCP app
- JAAS LoginModule
ISS: Identity Selector Service and STS
- Internal components (e.g. matcher, selector, H-Tag manager)
- Security Token Service (STS)
IdAS: Identity Attribute Service
- Application Programming Interface (API): HTTP/XML, WSDL, Local Language Interface(Java)
- Context Provider Interface (CPI)
- IdAS implementation
Example Context Providers
- File-based Context provider: for developers only (org.eclipse.higgins.context.user)
- ECF Collab - Integration with ECF collab code
- ProfileShare provider: Simple "vcard" sharing context (uses ECF) (org.eclipse.higgins.context.profileshare)
- SSEContext provider: RSS+SSE implementation under development
- Common: org.eclipse.higgins.context.model - building block currently used by org.eclipse.higgins.context.user and by org.ecipse.higgins.context.profileshare and others. Will be replaced in M4 due to new M4 data model
Projects
Work areas that cut across components:
- InfoCard, WS-Trust Interoperability
- Security Policy profiles for relying parties
- Integration of an STS with Higgins Core
- ...etc.
- JAAS Interoperability - Create a JAAS LoginContext impl and embed Higgin Core within it. Create a new "user" context that uses JAAS KeyStore.
- Automated daily builds
- Demos