From: Krzysztof B. <kb...@un...> - 2020-01-06 08:45:00
|
Dear Sander, W dniu 06.01.2020 o 08:08, Sander Apweiler pisze: > Dear Krzysztof, > > It seems that it is lost in the database: Yeah, certainly. Any ideas whether this role was dropped during some of migrations, or maybe was missing from the very beginning? I.e. have you ever used this missing role on the system in question? Or you rather suspect that this is result of recent migration (if yes knowing start version would help)? > Because on other instances we have this role, do you know a database > query to create it? Yes, however this is pretty low level. You need to do this either on DB (SQL UPDATE) or export the JSON dump, fix it there, and import. In any case the missing role needs to be added to the JSON describing the attribute type. So in case of DB: 1. take backup :-) 2. in table ATTRIBUTE_TYPES identify PKEY (ID column) of record with NAME = 'sys:AuthorizationRole' and the current, malformed CONTENTS column value of the record. 3. update record CONTENTS column with the ID from the above point so it has the same contents as originally, but additionally the allowed part in syntaxState is as follows: "syntaxState":{"allowed":["Privileged Inspector","Anonymous User","Inspector","System Manager","Contents Manager","Regular User"]} (the rest should be intact - i.e. you will need to add this "Privileged Inspector", string) HTH KB |