Some OSLC Remote Applications require server-to-server communication, in scenarios where no user activity is involved in the browser, and so without a logged-in user. This is for example when a remote server is to discover in the background the capabilities offered by ${local-app-connector}, so they are known and ready to use when requested by the user. As detailed in ${anchor-title-consumers}, allowing server-to-server communication is done by configuring a Functional User on the consumer and marking the consumer key as Trusted.

Make sure to allow server-to-server communication when configuring consumers for following applications:

• IBM Engineering Systems Design Rhapsody – Model Manager (RMM)
• IBM Global Configuration Management (GCM)
• IBM Lifecycle Query Engine (LQE)
• IBM Link Index Provider (LDX)