spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How to Set-up and Perform Impersonation on PTC Integrity

Written by SPK Blog Post
Published on April 27, 2015

From time to time, if you are administering a PTC Integrity Lifecycle Manager you’ll need to be able to log into PTC Integrity as one of the users you support. If you want to avoid requesting their password (if your company uses LDAP to synchronize everyone’s PTC Integrity password with their corporate password, sharing passwords with anyone is not a good idea security wise), or forcibly resetting their password in the MKS Domain (if you use that), you can use something called impersonation.

NOTE: Impersonation can be a potential security hole. There is the possibility for a user to perform actions that are logged as another user who could potentially have administrator permissions.

In order to try to avoid any potential security pitfalls, the example I am going to walk through below will demonstrate how you can configure your administrator account (and only your administrator account) to impersonate other users.

Before you can start impersonating people on your PTC Integrity Lifecycle Manager server you need to create an ACL (Access Control List) to define who has access to the permission to do this.

To set up the Impersonation ACL in PTC Integrity Lifecycle Manager, perform the following steps:

1) In the PTC Integrity Administration client, expand the Permissions section and select the “All” node.

2) Next, right click on the mks ACL group, and select “Create ACL.”

3) This will open the “Select ACL Entries to Add” dialog

4) Next, define the user or group you wish to allow impersonation of.  In this case I want to allow for the impersonation of the “everyone” group.  Therefore I have named the ACL mks:impersonate:group:everyone

5) Last but not least, I select the administrator user, to implicitly state which user has permissions to impersonate under this ACL.

6)  Once you select “OK” to apply your new ACL you will see it appear in the ACL lis

Creating the ACL to allow for impersonation is just the first step.  If you actually want to perform Impersonation you need to invoke it from a command prompt window.  You cannot invoke impersonation through the GUI.  You can use the command line to create a GUI session and instantiate the connection using the impersonateuser flag to create a session as the impersonated user.  The command to do so is as follows:

im issues –hostname=serverHost –port=serverPort –user=administrator –password=yourAdminPass –impersonateuser=impersonatedUser –gui

This in turn will open the following window for you:

From here, everything that is performed will be as if you were logged in directly as a given user in the system. And best of all, the only people who will have access to this impersonation functionality as it is configured are those people who already have access to your administrator account.

The ability to impersonate any given person within your PTC Integrity server can go a long way in determining what the problem is when one of your users calls you complaining that a certain trigger or critical piece of functionality isn’t working.

Next Steps:

Latest White Papers

Related Resources

CarFax + Roadmunk

CarFax + Roadmunk

For 37 years, CarFax has been trusted by millions of Canadians and Americans to supply them with vehicle history reports to help them make more informed purchasing decisions. What Did Roadmapping at CarFax Look Like Before Roadmunk? If you’re on a mission to bring...

How Cloud-Based CAD Is Changing the Future of Collaborative Design

How Cloud-Based CAD Is Changing the Future of Collaborative Design

Traditional desktop-based CAD tools, while powerful, can have a hard time meeting the growing demands of modern engineering teams. They need better connectivity, scalability, and flexibility. That’s why cloud-based CAD (Computer-Aided Design) is quickly becoming the...

Meet the Experts: Darla Kost

Meet the Experts: Darla Kost

Darla Kost started as a DevOps engineer at SPK and Associates in July of 2024. Prior to joining SPK, Darla was an engineer in the U.S. military. Now, she works with similar tools and focuses much of her time on managing infrastructure and automating processes.My Role...