Hi Karen:
To add a little to Marius' reply, I believe these are the constraints on impersonation via REST API based on the last time I tested this:
- Anyone in Admin + DataAdmin groups:
- Impersonate another Admin group member: NO
- Impersonate a DataAdmin group member: YES
- Impersonate a SecurityAdmin member: YES
- Impersonate any non-Admin group user: YES
So, in short: anyone who is not in the Admin or DataAdmin group cannot impersonate another user (this restriction extends to SecurityAdmin group members).
Also, note that there are Info level login events that you should see when impersonation takes place, for instance:
61456 [7] INFO 2020-09-21 15:56:16.436 TM1.Login User Admin authenticated, attempting to impersonate user Joe
This means you've got an audit trail for any user impersonations, too, meaning an admin can't go in and change data as a user without there being a record of the impersonation.
Hope that helps!
------------------------------
Michael Cowie
QueBIT Consulting
Tuscaloosa AL
------------------------------
Original Message:
Sent: Thu February 04, 2021 07:31 AM
From: Karen Hewitt
Subject: TM1py 1.6
With the impersonate functionality could any user impersonate any other user or could only an admin in the tool use the impersonate feature? My concern would be another user who knows TM1py uses impersonate feature to become an Admin.
------------------------------
Karen Hewitt
Original Message:
Sent: Wed February 03, 2021 05:16 AM
From: Marius Wirtz
Subject: TM1py 1.6
Hello TM1 & Planning Analytics community,
Last week we released TM1py 1.6.
It's a big release with interesting new features like impersonation and improved write speed.
You can find an overview of the release here:
https://code.cubewise.com/blog/tm1py-v1 ... -available
------------------------------
Marius Wirtz
------------------------------
#PlanningAnalyticswithWatson