Hi All, I have a use case scenario where I need to set the cipher suite order list within our SSL transport URI. We are setting the cipher suite list as well via transport.enabledCipherSuites which works as expected. However when we attempt to set transportr.UseCipherSuitesOrder It does not appear to be reflective like I would expect, and the client is still setting the order. If we had control of all the clients, we could dictate the order within the client, but since most of the clients are outside our development control, this would be the method to dictate the order that is set in the URI and fulfill this contractual obligation. Has anyone tried this before and had any luck setting the cipher order?
-- Thanks, Joe Carder | Enterprise Architect, Open Logic Perforce Software<http://www.perforce.com?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link> P: 866.399.6736<tel:+1%20612-517-0000> Visit us on: LinkedIn<https://www.linkedin.com/company/perforce?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link> | Twitter<https://twitter.com/perforce?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link> | Facebook<https://www.facebook.com/perforce/?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link> | YouTube<https://www.youtube.com/user/perforcesoftware?utm_leadsource=email-signature&utm_source=outlook-direct-email&utm_medium=email&utm_campaign=2019-common&utm_content=email-signature-link> This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
