[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] [sec] target EEs for JAAS integration work?
|
Foundation 1.1 sounds good as it does include the javax.security.auth.* packages as optional API.
http://jcp.org/en/jsr/detail?id=219Regards,
Rem
On 8/16/07, Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> wrote:
Something small would be good. Foundation
1.1 might be a good option?
Jeff
Hmmm... Looks like CDC/Foundation does not include the javax.security.auth.*
packages. I'm not sure if a JAAS implementation could be dropped on top
of it, but I wouldn't be surprised if it could. JAAS is pretty thin.
With respect to a LoginModule for 3.4, I expect we will develop several
(or explain how to use those in a typical JRE). The default configuration
will probably work with a standard format JKS/JCEKS stored in an appropriate
place for the platform (workspace, etc).
Yeah that pattern is a bit busted - perhaps an anonymous Subject when authentication
is not enabled is possible.
One of the plugins got renamed - swap org.eclipse.equinox.security.proxy
with org.eclipse.equinox.security.provider. Eventually, I'd like to collapse
org.eclipse.equinox.security.boot into the provider as well. That's under:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196988
-matt
---
Matt Flaherty
Security Project Lead, Lotus Notes & Eclipse Equinox
External: http://www.eclipse.org/equinox/incubator/security/
Internal: https://cs.opensource.ibm.com/projects/eclipsesec/
Hi Matt, Li, and all,
What is the target/supported EEs for the JAAS integration work? i.e.
is
it intended/expected to run on CDC 1.0/Foundation 1.0...or (what) others?
And if I'm not mistaken, I don't think some of the java.security.*
interfaces/classes are available in CDC 1.0/Foundation 1.0 so perhaps
CDC 1.0/Foundation 1.0 isn't in the picture at all.
Another question: Is there going to be a login module for Eclipse
3.4/Ganymede?
Also, after updating to the latest code from HEAD, I'm getting compile
errors in org.eclipse.equinox.security.junit plugin (see below for details).
Finally, if API design votes are being taken, I would vote for
SecurePlatform.getSubject()
rather than
subject = SecurePlatform.isEnabled( )
? Subject.getSubject( AccessController.getContext(
))
: null;
(in SubjectView class)
Thanks...looks like really good work. I'm working with it now
(creating/testing a new login module).
Scott
---compile errors in org.eclipse.equinox.security.junit----
Severity and Description Path Resource
Location Creation
Time Id
KeyManagerFactorySpiService cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyManagerFactoryProxyTest.java line 112 1187211206427
547995
KeyManagerFactorySpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyManagerFactoryProxyTest.java line 108 1187211206427
547994
KeyManagerFactorySpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyManagerFactoryProxyTest.java line 194 1187211206427
547996
KeyStoreSpiService cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyStoreProxyTest.java line 184 1187211206411
547986
KeyStoreSpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyStoreProxyTest.java line 180 1187211206411
547985
KeyStoreSpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyStoreProxyTest.java line 546 1187211206411
547987
The import org.eclipse.equinox.security.provider cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyManagerFactoryProxyTest.java line 28 1187211206427
547993
The import org.eclipse.equinox.security.provider cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
KeyStoreProxyTest.java line 35 1187211206411
547984
The import org.eclipse.equinox.security.provider cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
TrustManagerFactoryProxyTest.java line 31 1187211206364
547978
TrustManagerFactorySpiService cannot be resolved
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
TrustManagerFactoryProxyTest.java line 111 1187211206364
547980
TrustManagerFactorySpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
TrustManagerFactoryProxyTest.java line 107 1187211206364
547979
TrustManagerFactorySpiService cannot be resolved to a type
org.eclipse.equinox.security.junit/src/org/eclipse/equinox/security/junit
TrustManagerFactoryProxyTest.java line 192 1187211206364
547981
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
