CSM affecting the Webservice Configuration in Target Instance
CSM affecting the Webservice Configuration in Target Instance: Any subsequent CSM from Source to Target instance is affecting an existing Live Integration which uses Web Services from the OSC Application Composer. Web Service Configuration needs to be recreated and reconfigured.
We have deployed an OSC solution for our client and we've encountered a constraint relating to CSM that is hampering our migrations from lower environments to PROD.
We have an OAuth secured outbound web service configuration that is part of our CSM migrations. We have tried to make it environment agnostic (by using application profiles, etc.) to remove environment specific parameters like hostnames and OAuth credentials, but have found two areas where we are unable to do this. I've attached a screenshot that shows the web service config in our test OSC environment (Dev13). We are unable to alias the hostname for the URL parameter in the screenshot and our OAuth entries for the Client Credential Key and Credential Key for Switch Identify do not migrate as