[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Equinox Security and role-based UI contributions

That's great! We've been hoping to get some requirements in this area as well. The contribution in the incubator is a way to install the artifacts required to use JAAS (Configuration, LoginModule, CallbackHandler,etc) in the platform, and to manage the settings required to provide a single 'platform login'. A couple of items on the to-do list are integrating the login event into the lifecycle of Eclipse startup, and then into the contribution model as well. This sounds right up that alley.

We have a weekly call, and we've had some guests join us over the last few weeks. Maybe we should set something up?


Matt Flaherty
Security Project Lead, Lotus Notes & Eclipse Equinox

From: "Boris Bokowski" <bokowski@xxxxxxxxx>
To: "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>, "Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>
Date: 11/12/2007 03:45 PM
Subject: [equinox-dev] Equinox Security and role-based UI contributions

There is an ongoing discussion about how best to restrict the visibility of UI elements such as views, preferences, actions etc. based on the current user's role. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=201052

As pointed out by Scott Lewis on the bug (thanks!), there seems to be a relationship between this it and the Equinox Security incubator work:

I wanted to let a wider audience know about these two things, in the hope that people who know about one can comment on the other, or perhaps just follow what's going on.


Boris Bokowski
Eclipse Platform UI committer
IBM Rational Software, Ottawa Lab
equinox-dev mailing list