You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Note!! Please register for a free account to access the full content and also to participate in Q&A in the community

OMSH: Registering a Non-OCI Instance Where Management Station uses a Proxy That Injects Its Own Cert

edited Jun 2, 2025 4:38AM in Linux

Note!!Please register a free account to access the full content and also to participate in Q&A in the community

Applies To:

Oracle Cloud Infrastructure
OS Management Hub (OSMH)

Goal:

A non-OCI instance can be an on-premise machine or a 3rd-party cloud instance. If the local management station uses a proxy that injects its own certificate in HTTPS communications with OCI, then registering a non-OCI instance at the same location should have that proxy certificate or its signer/issuer certificate imported into a trust base used by the management agent (i.e. mgmt_agent) running on that non-OCI instance.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!