Skip to main content

Jama Connect Help

Protect the endpoint

The Jama Connect multi-adapter client sends JSON requests with Content-Type: application/json. It doesn’t add an adapter API key, Authorization header, sign requests, or include URL credentials.

  • Use HTTPS with a certificate trusted by the Jama Connect environment.

  • Prefer a private network route to the adapter.

  • Restrict access with network or gateway controls compatible with the Jama Connect client.

  • Keep credentials out of the configured URL.

  • Keep unauthenticated test endpoints off the public internet.

  • Remove sensitive data from adapter logs and diagnostic responses.

If your security policy requires authentication that the Jama Connect client can’t provide, use a compatible gateway that you control or contact Jama Software Support before using the adapter in production.

The adapter is available at the complete operation URL, can reach the selected provider and model, and returns responses in the documented Jama Intelligence Gateway adapter format.