Adding support for insecure TLS while deploying to TIBCO Platform when using Self-Signed Certificate #732
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
****What's this Pull request about?
Introduce a new property: -Dcom.tibco.platform.tls.insecure=true to allow deploy to TIBCO Platform even the certificate hasn't been trusted.
****Which Issue(s) this Pull Request will fix?
This fix the issue to deploy using maven plugin to customer environments with self-signed or internal PKI certs that are not part of the default truststure.
Id and Summary of the issue that the Pull Request will resolve:
N/A
****Does this pull request maintain backward compatibility?
Yes, only do the change if the property is set to true.
****How this pull request has been tested?
Tested from BWCE 2.9.2 and TIBCO Platform 1.1.0 (CP 1.3.0)
Mention the test scenarios.
maven install to a BWCE app, and check it was succesfully uploaded and deployed on the DP.
****Screenshots (if appropriate)
N/A
****Any background context or comments you want to provide?
N/A