IMHO maintaning/getting user properties from two APIs is not going to be clean. Let me suggest a completely different approach:

- Lets use only authentication from UserManager.
- Lets completely bring in the concept of user profiles into Identity Solution (When users use it with the default user store). - In this case both CardSpace and OpenID will have multiple profile functionality.
- We will have our own UserPropertyreader interface
- In cases where the user store is something else other than the default UserStore (LDAP, JDBC) we will *not* support multiple profiles, since user properties are given by the third party user store.

Thoughts?

Thanks,
Ruchith

Dimuthu Leelarathne wrote:
Hi All,

After studying the requirements very closely I came to the conclusion
that this is OpenId requirement. Why?

Say there is a user with the name Namal. And Namal has two profiles by
the name Profile-A and Profile-B.

In Profile-A Namal has the address - No 59, California, USA
In Profile-B Namal has the address - No 50, Colombo, Sri Lanka
I think this is a OpenID requirement. Therefore I added this to Identity
Solution.

The functions are available in OpenIDProfileAdmin.java

I have committed this to the revision 13788.


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Identity-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/identity-dev

Reply via email to