Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [higgins-dev] Updating Password with IdAS

Specifically for updatePassword:  David originally brought this up.  It would be good if people could visit that bug and add any characteristics they believe that method should have.
I'll log another for the general case of blind updates (Tom pointed out that at least the JNDI using LDAP CP is not completely capable of knowing when an attr is present yet non-readable versus non-present).
On the IRC, Dale also mentioned the need for a verifyPassword operation.  I'll log another for that.

>>> "Jim Sermersheim" <jimse@xxxxxxxxxx> 6/18/07 4:05 PM >>>
Well, the IdAS data access model we arrived at was one somewhat analogous to the way one typically navigates, accesses, and updates other kind of hierarchical data.  Prior to that model, we had one where the caller specified the data, action, and value being performed for updates (people disliked that).
With the current access model, I think you'd have to get the CP to cooperate for most cases like this.
First, I'm not sure why it should fail if you ask for any attribute which it doesn't have.  I assumed the call to IDigitalSubject.getSubject(String cuid, Iterator attrSelectionList) would silently ignore any attributes in the attrSelectionList that don't exist or are not returnable for the subject being read.  This needs to be documented in the Javadoc.
In cases where an attribute exists, can't be read, but can be updated, I think the CP could return an attribute with zero values.  This again would need to be clarified in the javadoc (a note added that an attribute with zero values is allowed when the consumer is not allowed to view the values).  Of course, this would be subject to any other access controls which might deny the consumer from seeing even an empty attribute.
For passwords specifically though;  David brought up some password modify use cases at the Austin F2F and noted that maybe password modify was a unique enough operation that it deserves its own API.  Something that can accommodate proof of old password, challenge/response negotiation, CP-generated password, etc.  I made a quick note in but haven't done anything beyond that.

>>> "Daniel Sanders" <dsanders@xxxxxxxxxx> 6/18/07 3:25 PM >>>
Currently, it appears to me that I can only change existing attribute values on a digital subject if I first "get" them.  But a digital subject's password is sort of a special case.  The JNDI provider cannot really "get" that particular attribute.  It will fail if I ask for it specifically, and it will not return it if I simply ask for all attributes.  I need a way to change an attribute's value without getting it first.  Is there any way to do that in IdAS today?
I guess in general, this is needed for attributes where you are allowed to update them, but cannot to read them.

Back to the top