Unable to receive any error while replacing email of a non-provided user with another user's account name

Description

As per test step 1.12 of Account tool, changing email of a non-provided user with another user's account name should not be allowed but I was able to change. Please find the attached video as proof.
Server: https://qa20-mysql.nightly.sakaiproject.org/portal/site/

Web Browser: Google Chrome version 78.0.3904.97

Attachments

1

Activity

Show:

Shawn Foster December 16, 2019 at 1:44 PM

I created to have user.email.allowduplicates documented in default.sakai.properties.

Brian J. December 16, 2019 at 1:42 PM

And the properties files need to be updated accordingly, as they're all set to false on the old property

Shawn Foster December 16, 2019 at 1:38 PM

I think the property that we are looking for is:

searched the Sakai master code for the property that and mention above (enable.duplicate.email) and could not find it being used. Therefore, the test script needs to be updated to reference "user.email.allowduplicates=false".

Earle Nietzel December 16, 2019 at 1:33 PM

 typically we don't set non OTB properties outside of master experimental

Shawn Foster December 16, 2019 at 1:30 PM

, can you assist getting this property enabled for 20? What is the process for testing non-default properties for branches? Should the test script be changed to assist with this step?

Non-Issue

Details

Priority

Affects versions

Components

Assignee

Reporter

Environment

Google Chrome
Created December 12, 2019 at 12:56 PM
Updated December 23, 2019 at 5:19 PM
Resolved December 16, 2019 at 1:39 PM