[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [higgins-dev] Agenda for Higgins developer call March 26 at noon ET
|
Hi Sergey, Alex,
I tried removing the IContext references from Authentication Materials classes (e.g. AuthNNamePasswordMaterials).
But this seems to be not so easy, since some CPs (e.g. idas.cp.xml) really make use of this. If I understand their behavior correctly, they treat the Authentication Materials (e.g. username + password) like attributes inside the IContext. I find this confusing, but if we remove it it may break a lot of things.
Anyway, I tried making AuthNNamePasswordMaterials a little more JavaBean-like, by adding another constructor that doesn't require IContext.
Maybe you like to take a look at it, and maybe you have some idea to make it better..
Markus
2009/3/27 slyakhov
<slyakhov@xxxxxxxxxxxxxx>
> I also thought that it would be best to just make them
Serializable Java Beans..
+1.
> Do you think we could remove these IContext references?
Yes, there is no sense to use IContext to
instantiate credentials object. I suppose, Jim added
IContext.buildAuthNAttributesMaterials() method in order to ensure that IContext
suppots appropriate credentials type. But if IContext does not support some type
of credentials it could throw UnsupportedCredentialsException in IContext
.open() method instead.
Thanks,
Sergey Lyakhov
----- Original Message -----
Sent: Thursday, March 26, 2009 3:53
PM
Subject: Re: [higgins-dev] Agenda for
Higgins developer call March 26 at noon ET
Hi Alex,
I totally
agree!!! I also thought that it would be best to just make them Serializable
Java Beans.. But the problem is that currently some of the Authentication
Material classes need a reference to an IContext. I never really understood
that.
Do you think we could remove these IContext references? If yes,
then everything would be much simpler and we could just do what you
suggest..!
Markus
On Thu, Mar 26, 2009 at 1:19 PM, Alexander Yuhimenko
<ayuhimenko@xxxxxxxxxxxxxxxx>
wrote:
Hello
Markus,
Just some thoughts about IdAS Authentication Materials http://wiki.eclipse.org/Authentication_Materials.
It's
really useful to have identifiers of Authentication Materials. But It
seams Authentication Material may be just Serializable Java Bean.
*
If it's serializable bean, it'll be able to be cached with distributed
cache framework (ehcache,jbosscache,...) on server side between few server
nodes.
* Instead of defining methods for serializing (to/from XML,
String, etc.) it will be more clear and flexible to implement serializing by
using other "manage bean" class. For example, current
org.eclipse.higgins.idas.common.AuthNNamePasswordMaterials provides is not
clear API, it may be make sens to move business logic to "manage bean" or
"utility" class and leave just get/set for username an password
fields.
--
thanks,
Alexander Yuhimenko
<AYuhimenko@xxxxxxxxxxxxxx>
_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev
