I’m trying to integrate Connections EE and updates into Notes so 1 of the steps is the export the xml files from Connections and then import them into the widget catalog. I have the admin role so I can approve the widget, so far so good. If you look at the widgets by approval view on the server you see them listed under ‘Approved’.
Next, the changes are replicated to the local widget catalog but that same view always shows the same widgets as ‘Needs approval’ and as a consequence, the gadgets won’t load since they have not been approved (error in the Notes log file). Whatever I do, on local the status is always ‘needs approval’ while in the documents you see that I have approved them.
It’s not related to the Connections widgets, it’s the same for the opensocial test gadget. Approved when looking on the server, and needs approval on local. Already tried enabled consistent ACL and then creating a new replica but the situation doesn’t change.
Any suggestions?
tx,
Stijn.
Subject: RE:Connections widgets never approved on local
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIDwvZm9udD48Zm9udCBzaXplPTMgZmFj ZT0ic2Fucy1zZXJpZiI+U3Rpam48L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYi Piw8L2ZvbnQ+PGZvbnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPg0KPGJyPg0KPC9mb250Pjxm b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj48YnI+DQpDb3VsZCB5b3UgZm9sbG93IHRoZSBz dGVwcyBiZWxvdyBhbmQgaGVscCB0byBjaGVjayBzb21lIHBhcmFtZXRlcidzIHZhbHVlPw0KVGhl biB3ZSBjYW4gZmlndXJlIG91dCB3aGF0J3MgdGhlIHByb2JsZW0uIFRoYW5rcy4gPGJyPg0KMS4g T3BlbiB0aGUgQ29ubmVjdGlvbiB3aWRnZXQgb24gdGhlIGxvY2FsIGNhdGFsb2c8L2ZvbnQ+PGZv bnQgc2l6ZT0zIGZhY2U9InNhbnMtc2VyaWYiPg0KPC9mb250Pjxmb250IHNpemU9MiBmYWNlPSJz YW5zLXNlcmlmIj48YnI+DQoyLiBSaWdodCBjbGljayB0aGF0IHdpZGdldCBkb2MsIGNob29zZSCh sERvY3VtZW50IHByb3BlcnRpZXOhsTwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJp ZiI+DQo8L2ZvbnQ+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCjMuIEluIHRo ZSAybmQgdGFiIG9mIERvY3VtZW50IHByb3BlcnRpZXMgZGlhbG9nLCBDaGVjayB0aGUgdmFsdWUg b2YgNCBmaWVsZHM6DQpBUFBST1ZFUiwgc2VjdXJpdHlSZXZpZXdOZWVkZWQsIFhNTFJFVklFV05F RURFRCwgY2FwYWJpbGl0aWVzLjwvZm9udD48Zm9udCBzaXplPTMgZmFjZT0ic2Fucy1zZXJpZiI+ DQo8YnI+DQo8L2ZvbnQ+PGltZyBzcmM9Y2lkOl8xXzE0Q0RBODJDMTRDRDlEMEMwMDEwQkU1NjQ4 MjU3QzA2IHdpZHRoPTQwNyBoZWlnaHQ9MjgwIHN0eWxlPSJib3JkZXI6MHB4IHNvbGlkOyI+PGZv bnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPjxicj4NCjQuIENoZWNrIHRoZSBBQ0wgc2V0dGlu ZyBmcm8gdGhlIEFQUFJPVkVSIG9uIHRoZSBsb2NhbCByZXBsaWNhLiBBUFBST1ZFUg0KaXMgZXhw ZWN0ZWQgd2l0aCAnW0FkbWluc10nIHJvbGUuICZuYnNwO0NvdWxkIHlvdSBnaXZlIGEgc2NyZWVu IHNob3QgZm9yDQp0aGUgQUNMIHNldHRpbmcgb2YgQVBQUk9WRVIgb24gdGhlIGxvY2FsIHJlcGxp Y2E/IDwvZm9udD4NCg==
Subject: Found it !
3 elements have to be in place:
-
a user has to be listed in the ECL with the ability to configure widgets → was in place
-
user needs to have the admin role in the widget catalog → was in place
-
widget had to be approved → was in place
the thing that wasn’t correctly configured is that it should actually be ‘a user’. In my situation, the user had access in the widget catalog via a group with the correct role. This way you can approve the widgets on server side but on local they are not (probably since the signature doesn’t validate correctly). I’m also using a consistent ACL, don’t know if that’s required.
To correct the situation:
-
add the user explicitly to the ACL of the widget catalog
-
remove approval and re-approve widgets
-
replicate the changes to local
You should now see that the widgets are also approved on local.
rgds,
Stijn.
Subject: The root cause of this issue
In widget catalog, we are using @IsDocSignatureValid function to verify whether the widget doc has been approved. But there is a known issue SPR # YZLN93H7CN Link Notes://Porthos/85256055004781F8/A31656DDFB57FC028525747300577142/747ABF4B52D0997448257AE50018FC9A for @IsDocSignatureValid function. That is "
When accessing a local replica, @IsDocSignatureValid does not return the correct result if signer belongs to a group".
So the signer can’t be a group. It must be a user. That’s why a single user works, but not for a group.