corrad82-4s
corrad82-4s
Hello @tdonohue , we are interested in working this issue and #1610. Our estimation is 16 hours
Hi @tdonohue , we have spent so far about 10 hours in analysis. We tried to restore a behavior present in version 7.1, but it won't resolve problems here reported....
Hi @tdonohue , thank you for your feedback. I agree with you about the fact that we need to be cautious and avoid information exposure. In some scenarios we could...
Hi @tdonohue , hello everybody, as per what commented in https://github.com/DSpace/dspace-angular/issues/1736#issuecomment-1209126231, this issue seems to be more complex than expected. A solution could be force update of facets in case...
Hi @tdonohue , thank you for your comments. We will take in charge requested changes. I agree, having both (different) validations in place lead to a not optimal User experience....
Hi @tdonohue, yes, I definitely agree in removing minimum lenght validation. Current backend logic, presented with related backend PR [#8404](https://github.com/DSpace/DSpace/pull/8404/) does not expose an endpoint to validate password, but invokes...
Hello @tdonohue , thank you for your approval. Our developer pushed latest required changes.
Hi @tdonohue , we, as 4Science, can look at this issue. Feel free to assign it to us. Thank you
Angular related PR has been opened: https://github.com/DSpace/dspace-angular/pull/1776
As possible solution, we think following steps could be done. Step 1 - user can change password only if current authentication method is "password" and if he / she is...