On-premise proxy adapter configuration

some clients have a business requirement to expose internal on premise applications to external users, while not making the applications public such configurations enable secure access while maintaining control over data and traffic flow within your corporate boundaries you can bolster security and compliance requirements by keeping sensitive data on premise, not sending it directly to a cloud based service without compromising service access accommodates such circumstances by supporting websockets, which enable on premise poxy adapters broadening your service reach without comrpomising security configuring websocket complete the following procedure to integrate a proxy adapter using a websocket create a wsmesh token the wsmesh token can be generated by directly using the wsmesh swagger api page it can also can be generated in the following two ways core is deployed in the environment from the main menu , go to console → developer console in the api documentation section, select platform as application and wsmesh as service core is not deployed in the environment go to the tenant host select the user name select developer , then swagger select platform wsmesh from the dropdown menu use the api below for token creation api /api/wsmesh/v1/config/tokens \[post]url https request parameters { "broker" "mcmp\ devops intelligence\ service", "name" "name of the token", "single use" false } please make sure wsmesh service is enabled for the tenant create a uuid for the proxy adapter generate a uuid using the version 1 uuid generator found at the online uuid generator web site this id will be the proxy id used to identify the proxy adapter for the kmoa console onprem instance deploying a generic proxy adapter using helm chart complete the following procedure to deploy a generic proxy adapter download a generic proxy pod image from the file server the file server swagger can be accessed in two ways core is deployed on the environment from the main menu , go to console → developer console in the api documentation section, select as application and file server as service core is not deployed on the environment from the main menu , go to services → platform services → devops click on settings & utilities and then, api explorer select fileserver from the drop down menu download the proxy adapter image using the api below api /dash/api/file server/v1/files/mcmp generic proxy tgz provide the file name and click execute select the download file link and save the file to your system download the proxy adapter image using the api below api /dash/api/file server/v1/files/mcmp generic proxy tgz provide the file name and click execute select the download file link and save the file to your system add a generic proxy adapter to helm and configure it add the image to the peer docker instance using the command docker load < mcmp generic proxy tgz add the generic proxy adapter chart repo to helm use the below file server api to create a token api /dash/api/file server/v1/config/tokens \[post] request paramenters { "broker" "mcmp\ devops intelligence\ service", "name" "name of the token", "single use" false} add repo by using the command helm repo add devops intelligence https replace file server token with the token generated on the previous step add the values below in fe proxy adapter helm/ generic proxy adapter/values yaml host kmoa ui tenant host url (e g kyndryl multicloud ibm com) ws token name token name (created in step 1) ws token token (created in step 1) proxy id unique id for the proxy adapter (created in step 2) ws adapter true protocol tower application application name request paramenters { "broker" "mcmp\ devops intelligence\ service", "name" "name of the token", "single use" false} add repo by using the command "helm repo add devops intelligence https " replace file server token with the token generated on the previous step add the values below in fe proxy adapter helm/ generic proxy adapter/values yaml host kmoa ui tenant host url (e g kyndryl multicloud ibm com) ws token name token name (created in step 1) ws token token (created in step 1) proxy id unique id for the proxy adapter (created in step 2) ws adapter true protocol tower application application name request paramenters { "broker" "mcmp\ devops intelligence\ service", "name" "name of the token", "single use" false} add repo by using the command helm repo add devops intelligence https replace file server token with the token generated on the previous step add the values below in fe proxy adapter helm/ generic proxy adapter/values yaml host kmoa ui tenant host url (e g kyndryl multicloud ibm com) ws token name token name (created in step 1) ws token token (created in step 1) proxy id unique id for the proxy adapter (created in step 2) ws adapter true protocol tower application application name install helm chart for helm version 3x x helm install <\<releasename>> devops intelligence/generic proxy adapter f values yaml namespace <\<namespace>> create namespace deployment should be successful without any issues adding credentials for specific tools using proxy id the following tools are supported now ansible argocd azure devops gitlab github jfrog jira (server oauth support) jira (cloud oauth support) servicenow sonarqube in the tools credentials page, add the proxy id created in the create a uuid for the proxy adapter step for onpremise support; the proxy id will be unique for every supported tool