http://rifers.org/downloads/rife/snapshots/rife-1.6-snapshot-20070429/
contains the IdentifiableUsersManager interface with only the 2
methods needed for a CredentialsUser to be identifiable.
On 28 Apr 2007, at 21:17, Geert Bevin wrote:
Hi Eskil,
verifyCredentials needs to return a long that uniquely and
uniformly identifies a user. This long can't be different for the
same user. Is this the case?
Besides that, you're right, Identified can't work unless your
CredentialsManager implements RoleUsersManager. There are several
methods in there that are needed. I'm thinking of creating another
interface called IdentifiableUsersManager that contains the getLogin
(long userId) and getAttributes(String login) methods which are the
ones that are required by the Identified element.
Best regards,
Geert
On 28 Apr 2007, at 15:44, Eskil Lauritsen wrote:
Seems like we concluded too soon on the state of our LDAP integration
When we are logged in via LDAP, the
RoleUserIdentity identity =
RoleUserIdentity)getRequestAttribute
(Identified.IDENTITY_ATTRIBUTE_NAME)
returns a null pointer.
Can this be because the method verifyCredentials in LDAPUsers only
returns an auto incrementing long int? Do we have to implement a
datastructure similar to mUsers to avoid this null pointer?
--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
Rife-users@uwyn.com
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
Rife-users@uwyn.com
http://lists.uwyn.com/mailman/listinfo/rife-users