I also recommend you reconsider deploying LDAP, it is appropriate in a college setting for more than just DSpace.
If you want to do this the hard way, then I suggest you use row-level locking [1] on the specific row of the "eperson" table [2] that you need to protect. Please note that this feature is only available as of the latest release of Postgres - 9.5. Alternatively, you can change the DSpace source code to disallow password changes for the password authentication method. If you just change it to false, it will be effective for all users. You should only set it to false for the specific username you want to prevent from changing their password. [1] https://www.postgresql.org/docs/9.5/static/ddl-rowsecurity.html [2] https://wiki.duraspace.org/display/DSDOC5x/Storage+Layer#StorageLayer-RDBMS/DatabaseStructure [3] https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/authenticate/PasswordAuthentication.java#L108 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Mon, Nov 14, 2016 at 9:53 AM, arjun k <[email protected]> wrote: > Due to some problem,considering as an engineering college LDAP method is not > a good sugestion.i have already tried this once. If there is any other way > please help me? -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
