Timeline for Tridion Event System with specific User
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2019 at 9:07 | comment | added | Alvin Reyes | For those new to the concept, @RickP answered a few questions I had on ElevatePrivileges. For fun, I "illustrated" the concept using virtual Lego for TDS 2017. | |
| Aug 22, 2019 at 7:49 | comment | added | Quirijn | In that case, I think this is the easiest solution for Arulmozhi's problem. | |
| Aug 22, 2019 at 6:27 | comment | added | AntonM | No, there are no extra requirements (like being an impersonation user) for the current user. We do not consider it a vulnerability, but a feature ;) Assumptions here are (1) you have to be a system admin in order to deploy event handler and (2) as a responsible admin, you understand what this extension does. More to that, ElevatedPrivilegesScope API can only be used in the event handler. If you try to use it anywhere else (in stand-alone TOM.NET application, for example), you'll get InvalidActionException. | |
| Aug 21, 2019 at 13:37 | comment | added | Quirijn | Interesting, I didn't know about this. Would the current user have to be configured as an impersonation user? If not, doesn't this constitute a major vulnerability? | |
| Aug 20, 2019 at 13:05 | history | answered | AntonM | CC BY-SA 4.0 |