Applies to
-
OSLC Connect for Windchill 3.5+
-
OSLC Connect for Jira 2.7+
-
OSLC Connect for Confluence 1.1+
Problem
Admin entered a Root Services URL whose content can be accessed but doesn’t contain the expected OAuth properties nor any OSLC catalog.
Cause
OSLC Connect asked for a Root Services document, but the response is not a Root Services document.
Resolution
You should attempt the following step by step:
-
double check the Root Services URL, for it is possible it is incorrect or invalid
-
if you get a login page when attempting to reach the Root Services URL
-
check whether OSLC Remote Application is not overly secured. The Root Services URL serves as a discovery document and must be freely accessible.
-
-
if OSLC Remote Application is behind a reverse proxy, and you get an error document that looks to be coming from the reverse proxy
-
check whether OSLC Remote Application is properly reachable by reviewing the reverse proxy configuration
-
