Possibility to adopt the Windchill login credentials in Toolkit apps
1. What product and version are you running?
We are currently working with Creo Parametric 7.0.11.0 and Windchill 12.0.2.11.
2. What is the problem?
In addition to our own requirements, this idea also results from the PTC article CS289412.
If you have already registered a Windchill server in Creo Parametric and logged in there, there is no way to adopt this login credentials in a Toolkit app and access Windchill data using the REST API.
The workaround described below must be used for each additional Toolkit app.
After a password change, which must be done every few months by all users in our company, this means that the new login credentials must be entered several times after the Creo start.
This is very inconvenient and cumbersome for the users and does not meet with their understanding.
In addition, extreme care must be taken when programming a login data query and saving the login credentials to ensure that no mistakes are made in terms of security.
It would therefore be a great advantage if you could easily adopt the Windchill login credentials of an already authenticated Creo session into your Toolkit app and use them for Windchill access via the REST API.
3. Are you using a workaround? If yes, please describe it.
The current workaround is that the Toolkit app requests the login credentials at startup.
This data is then stored in encrypted form on the computer in a file or SQLite database.
The next time Creo is restarted, the login credentials can then be read and decrypted again.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
For example, just as there is a ProServerActiveGet() function to get the alias of the currently active server, a ProServerActiveCredentialsGet() function could be provided to return the username and password of the currently active Windchill session.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
I support about 300 Creo Parametric users that work with Windchill.
The loss of productivity is less of a problem here: every few months, after the password change required by IT security, users spend 5 minutes entering the new password when starting Creo.
On the one hand, this is more about the acceptance problem among users, who wonder why the hell they have to enter the same password several times in succession.
On the other hand, life could be made much easier for the Toolkit developers if they no longer have to worry about getting and saving the Windchill login credentials.
