Upgrade to Windchill 13 breaks REST API

[Dobi]

Version: Windchill 13.0

Use Case: Previously working REST API GET example in Windchill 12 now throws a "The requested resource [/Windchill/oauth/servlet/odata/v5/ProdMgmt/Parts] is not available" error.

Description:

I had a set of examples in Postman working when we were on our Windchill12 installation. Upgraded to Windchill 13 in December and I went to dust of the examples. Same GET calls now throw this error.

For the sharp-eyed, yes this calls the v5 of the API that is deprecated. The same result, though, happens on the latest v7 version. 

I confirmed that the Azure to securityContext.properties and wt.properties file settings are correct but Windchill 13 does have some additional lines in the securityContext file. 

If I try the same from the Windchill interface, everything works fine for the same URL (sans the oauth piece needed for SSO).

[HelesicPetr]

Hi @Dobi 

I guess that you have a trouble with authentication.

oauth is in your address but this is not correct and system tells you that the source is not available/ not found.

reason is that you use wrong address to the server and to the API

PetrH

[Dobi]

Hi @HelesicPetr 

oauth in the address was (WAS) the correct setting for OAuth2 links in Windchill 12 that work with SSO. That's the bit that I'm asking about now because it no longer works in Windchill 13. 

Removing that requires gives an SSO error because authentication doesn't happen with active directory. 

[HelesicPetr]

Hi @Dobi 

I guess that you should solve it on the SSO service that does the redirection the Windchill address. 

Or check if there is new version of the oauth function that might be changed.

PetrH

[Dobi · Accepted solution]

Resolved!

The issue was that in the OAuth setup I forgot to update the web.xml file per the instructions: https://support.ptc.com/help/windchill/r13.0.0.0/en/#page/Windchill_Help_Center/WCAdvDeployGuide/WCAdvDepAuth_ConfigAltAuth_RegisterScope.html

That's where the /oauth*/ bit in the URL comes in that was ultimately throwing the error.