Yep, value(s) for read-only schemas are modifiable only via internal
code [1], e.g. via DAO.
[1] https://ci.apache.org/projects/syncope/2_1_X/reference-guide.html#plain
On 24/01/19 16:58, pcrowder wrote:
I found nothing in the logs. Set everything to debug. No warnings or errors.
Using version 2.1.2 of Syncope.
Did some experimenting and this is what I found:
1. Using the patch method.
- The accountReviewDate was read only and a patch will not set a read only
value. If the read only flag is reviewed then the value is written to the
database.
- Neither value will display in the console (accountExpiryDate or
accountReviewDate) when editing a user.
- If you edit the blank field in the console (accountExpiryDate), a second
entry is written to the database (uplainattr and uplainaatrvalue). These
values now show up in the console.
2. Using UserDAO to save the values (no patch).
- Both values are written to the database even the read only field.
- Two values are written for the read only field (accountReviewDate).
- The read field displays in the console (accountReviewDate) but the other
field does not (accountExpiryDate).
- Editing and saving a new value for accountExpiryDate writes a new value
to the database and that value if visible in the console.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
