Andrea, re: 1.) since dspace.cfg is already a bloated monolith, I would ask the 
question, is there a valid use case for both sides of the configuration 
(on/off)?  If there is one satisfactory behavior, perhaps we can save adding an 
unnecessary switch to configuration.

Also, re: 2.)  for the many sites that don't use LDAP at all and aren't 
concerned with the value (or lackthereof), should we conditionally display the 
netid if it is non-null?


--
sands fish
Software Engineer
MIT Libraries
Technology Research & Development
sa...@mit.edu<mailto:sa...@mit.edu>
E25-131




On Mar 29, 2010, at 3:50 AM, Andrea Bollini (JIRA) wrote:


    [ 
http://jira.dspace.org/jira/browse/DS-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Bollini updated DS-524:
------------------------------

   Description:
Editing an eperson record from the WebUI we lost the netid value.
The only way to prevent this is set to true the property: ldap.enable

The property is related to LDAP so I'm not sure if there is other implications 
to use it... anyway, we need to separate these two concerns.
I propose to:
1) add a new configuration property to decide if the webUI is allowed to change 
the netid value; the authorization logic should be checked in the Servlet and 
not only on the client side as now is
2) always show the netid field, when appropriate as a readonly box

We need to check also the XMLUI to get a common behaviour.

 was:
Editing a record from the WebUI we lost the netid field.
The only way to prevent this is set to true the property: ldap.enable

The property is related to LDAP so I'm not sure if there is other implication 
to use it... anyway, we need to separate these two concerns.
I propose to:
1) make a new configuration property to decide if the webUI is allowed to 
change the netid value; the authorization logic should be checked in the 
Servlet and not only on the client side as now is
2) always show the netid field, eventually as a readonly box

We need to check also the XMLUI to get a common behaviour.


Eperson netID is lost editing the record from the webUI
-------------------------------------------------------

               Key: DS-524
               URL: http://jira.dspace.org/jira/browse/DS-524
           Project: DSpace 1.x
        Issue Type: Bug
        Components: JSPUI
  Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0
          Reporter: Andrea Bollini
           Fix For: 1.6.1


Editing an eperson record from the WebUI we lost the netid value.
The only way to prevent this is set to true the property: ldap.enable
The property is related to LDAP so I'm not sure if there is other implications 
to use it... anyway, we need to separate these two concerns.
I propose to:
1) add a new configuration property to decide if the webUI is allowed to change 
the netid value; the authorization logic should be checked in the Servlet and 
not only on the client side as now is
2) always show the netid field, when appropriate as a readonly box
We need to check also the XMLUI to get a common behaviour.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to