Michiel Meeuwissen wrote:
I dont want to go into the discussion -if- the returned node should be virtual or not(Maybe it would an option to always have an mmbaseusers with depending of the security implementation 1 or more virtual fields.)What's the point of Nodes? That they can have related nodes. So I'd say that this associated node should preferrably be a real, existing node, and the way to associate real nodes to a security account should be configurable in the security implementation. E.g. I ussually link mmbaseuser objects of cloud context security to people node (using its 'account' field), but I think that should be somehow pluggable, because it is no part of the security implementation, it's only a link to a cloud model.
, but i really should find it handy to put an password
field in it.
With this field we can change passwords, if we have write rights on the field.
--
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "INSTALL84.exe" was believed to be infected by a virus and has been replaced by this warning message.
Eduard Witteveen +316 414 789 23
