[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Granting permissions for usage of Bundle
- From: BJ Hargrave <hargrave@xxxxxxxxxx>
- Date: Tue, 15 Apr 2008 10:04:10 -0400
- Delivered-to: email@example.com
In general, the management of permission
is best done by a management agent: a bundle (or set of bundles) tasked
with managing the set of installed bundles including the security policy.
Enforcing permissions of course means that a SecurityManager is installed.
In order to modify the permissions on
CPA, the caller must have AllPermission. So, in your example, bundle A
would need AllPermission to modify the permissions so that only bundle
B can import a specific package. Bundle A is then a "super user"
which seems wrong.
||"Srijith Kochunni" <ksrijith@xxxxxxxxxx>
||2008/04/15 07:03 AM
||[equinox-dev] Granting permissions for
usage of Bundle|
I have a bundle(A) from
which I am exporting a package. I want to ensure that this package can
be imported only by another particular bundle(B) in the OSGi runtime. Have
been reading the spec about Conditional Permission Admin Service and Permission
Admin Service, but am finding it difficult to understand whether they do
provide such a facility and if so how it can be achieved using these core
Again I do not want
to use a separate Management Agent bundle to enforce this scenario, unless
there is no other option. It would be better if I could achieve this by
writing code in my consumed bundle alone. Any links to examples for using
Permission Admin Service / Conditional Permission Service would also be
equinox-dev mailing list