ELM Applications won't work with OSLC Connect for Windchill if their web application server is not configured following the IBM Support document 1288438
Recent versions of browsers such as Chrome and Firefox enforce by default a strict Same-Site cookie policy to prevent cross-site request forgery (CSRF) attacks.
This prevents OSLC interactions between friends from different domains to perform as expected. As such, OAuth interactions will fail, and previews and delegated dialogs will not display.
6.0.6.1 has a bug when displaying links. There is no warning when the user is
logged out of Windchill, and the links to Windchill parts are not displayed.
The customer of DOORS Next 6.0.6.1 can ask their support an IFix for this
bug.
DOORS Next 7.0.0 will add a warning to the user with an hyperlink that allows login to Windchill
and then the display of links.7.0.0 and the links
will not be displayed until connected to Windchill, without any warning.
7.0.0.7.0.0, when Global Configuration is enabled, an authentication problem may occur
at the first connection to Windchill. The OSLC Connect for Windchill APIs will require access to the
GCM application, which will be granted by IBM Engineering Test Management (ETM), even though it will display a seemingly unrelated
error message and leave an authentication window open. When this happens, close the authentication window and refresh the page. To fix this behavior, you may ask IBM for
a resolution of this defect.
Object References are not yet supported and are ignored in OSLC creation factories and creation dialogs. If you need to set an Object Reference, you have to edit the artifact using the native Windchill capabilities.