Cloudera Director fails to connect to CM after TLS is enabled [ Edited ]

[Sarthak]

I have a Cloudera Director managed deployment. 

After I enable TLS/SSL for the Cloudera Manager the CM URL is pointing to the new port i.e. 7183

However, Cloudera Director still points to the previous CM URL i.e. <CM-HOST>:7180.

Can you let me know how do I update my CM URL port in the director ? 

[Mike Wilson]

Director doesn't support TLS/SSL enabled CMs at the moment. We're aware and looking into this, but there's no timeline for its fix unfortunately.

[Sarthak]

Thanks for reverting. 

Any workaround for this issue ? 

Like if we can edit the port in some config file or database that the director uses ?