Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding support for insecure TLS while deploying to TIBCO Platform when using Self-Signed Certificate #732

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

alexandrev-tibco
Copy link

****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

@alexandrev-tibco
Copy link
Author

Could anyone merge this @mmilinds-tibco ?

@alexandrev-tibco
Copy link
Author

hey @sarundes any update?

@sarundes-tibco
Copy link
Collaborator

@alexandrev-tibco Approved from my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants