Thanks for the info. I've added some requirements to the given page.
Could you reference the IPZilla entries so that I (as committer) can
track? Once approved will the code be added in one of the Equinox
Also for my information...will this run on CDC 1.0/Foundation 1.0
runtime? Will it add to equinox-required set of bundles? (e.g.
extension registry, jobs, etc?)
Matt Flaherty wrote:
Yep, there's code in the pipeline -
it's in the IpZilla process at this point. Essentially, the
is geared towards plugging JAAS SPIs into the system (ie: LoginModules,
CallbackHandlers and Configuration) and providing access to a
Configuration and a LoginContext implementation that is extended in
ways: events, dialog-based prompting, etc. Principals are supported via
LoginModules, the big remaining work will be integrating the
into startup, things like the Jobs framework, and authorization
for extensions, etc.
For now, toss requirements into the
It might be time to start categorizing the security requirements into
for login/user authentication, credential management, code
etc. I'll do that this week.
equinox-dev-bounces@xxxxxxxxxxx wrote on
> I've heard a rumor :) that post-Europa there will be some JAAS
> integration bundles being contributed to Equinox for security
> enhancements (i.e. supporting platform-level
> hope, etc).
> Is there any way to find out/begin review/start contributing
> ideas/requirements/enhancements for this work for those of us not
> Equinox committers (i.e. other community members)?
> Just by way of example, for some time, ECF uses/extends the
> interface for it's concept of 'IDs' (user ID, process ID, service
> etc). Iff the JAAS integration work provides services and/or
> points to allow other plugins (ours and those built upon ours) to
> contribute Principals and Credentials to authenticated Subjects
> successful authentication, we would be most happy :).
> equinox-dev mailing list
equinox-dev mailing list