On 2/9/17 3:33 PM, Marek Posolda wrote:
On 09/02/17 16:32, Bill Burke wrote:
> LDAP No Import in master. I ended up creating a UserModel in-memory
> pojo, and passing it to the import command and that worked for most of
> situations. There were some other minor fixes to get it to work. The
> only issue I have now is that if there is no mapping for an update, no
> exception is thrown and the changes are just lost with no warning.
> Runtime should throw an error in this situation. Not sure the best way
> to handle it for the moment, so I'm going to let it stew in my brain for
> a little while.
What if UserStorageProvider has a method, which will return list of
updateable attributes/properties for particular user? The
non-supported attributes can be marked as read-only in the UI. LDAP
provider will look for what attributes it has mappers and just those
can be shown in UI as editable.
I'm not doing any UI work. Just want to make sure that if somebody
performs an illegal update, they get notified its illegal. I think what
you're saying will work. The information is there for attributes. For
group/role mappings is sort of, kind of is.
Bill