Skip to main content
avillanueva
avillanueva23-Emerald II
23-Emerald II
September 14, 2026
Question

Creo Parametric Browser defaulting to wrong SSO Authenticator

  • September 14, 2026
  • 4 replies
  • 13 views

This might be an “us” issue but we have an issue where the internal browser for Creo (version 9) is defaulting to the wrong SSO authenticator for Windchill when we try to connect Creo. We are in a company transition so our server exists on our old corporate network which we have opened up access to. On our laptops, we are logged in as users in the new company. In Chrome or Edge, we are able to create dual profiles in those browsers and leverage “other user” when connecting to Windchill. No issues so far. Also most all users do get this option in Creo and it has worked. Where we have seen this is if the user tried to connect with new company credentials and browser remembers it. Clearing cache seemed to fix this. 

I’ve tried all the steps in Creo to clear the cache, remove folders, to try and reset things but no luck. 

https://www.ptc.com/en/support/article/CS368331?source=search

Steps above did not work. We have removed the creo9ws folder and recreated it.  Is there someplace else I can look for this setting?

4 replies

MarcoTosin
MarcoTosin21-Topaz I
21-Topaz I
September 14, 2026

Hi Antonio,

I see that you're using different users, but the IP address from which the login requests are made it's the same or it's different?

 

Marco
avillanueva
avillanueva23-Emerald IIAuthor
23-Emerald II
September 14, 2026

How do you mean? From client side or are you referring to the SSO authenticator? PDMLink IP is the same. We have two laptops, old company and new company. Two network jacks on while connecting to different switches and networks. Yes, different users. We’ve seen it where the browsers get confused and switch to wrong authenticator (Microsoft Azure AD)  for new company instead of asking and allowing us to enter in the old company login. Clearing cache (or using browser profiles) typically fixed it.  I am suspecting that is the same issue going on here.

MarcoTosin
MarcoTosin21-Topaz I
21-Topaz I
September 14, 2026

In the past, we encountered issues when we ran tests to switch to Azure authentication for the test and production servers, which share the same IP address (that of the reverse proxy).

 

We resolved this by setting this configuration parameter to “yes.”

 

dm_allow_register_duplicate_ip yes

 

I don't know if this applies to your situation, but I'm sharing this information anyway.

 

This is related article

 

Error "Server already registered" when trying to register second Windchill server in Creo Parametric and/or Windchill Workgroup Manager

 

Marco
Terms & ConditionsAccessibility statement