Linux: /home//.config/conduktor/conduktor.Conduktor is now available on the #AWSMarketplace! We've been working hard with the AWS MSK team to integrate Conduktor and make it the best complement to your AWS MSK clusters. Windows: C:\Users\\AppData\Local\conduktor\conduktor\conduktor.vmoptions.MacOS: /Users//Library/Application Support/conduktor/conduktor.vmoptions.As a workaround it is possible to allow insecure localhost call in google chrome : chrome://flags/#allow-insecure-localhost I need to configure custom JVM options Ĭreate the file conduktor.vmoptions in your Conduktor personal folder and add as many "-D" as you want (only -D, no -XX), to set them when Conduktor starts (only on startup, it's not taken into account after): In some cases, enterprise network policies force the login callback form http to https. If your organization has its own self-signed CA and certificates, you can add trusted certificates within Conduktor from the welcome screen.Ĭertificates FAQ Login Callback is HTTP_S_ instead of HTTP My organization manage its own certificates / PKIX path building failed Unexpected end of file from server: something on your network prevents Conduktor to request our identity provider, auth0 (Conduktor -> ).Server so nothing specific to setup here. Let's Encrypt's CA, which is the one that emits the https certificate of our authentication The JVM embedded in Conduktor (Java 13+, if you are using the classic installation process) trusts Proxy returns Go to the settings, setup your proxy manually instead of the system proxy and and add an exception for *.conduktor.io This can causes some troubles such as: Unable to tunnel through proxy. By default, Conduktor uses your system proxy.You may have to add to some allow-list or something. Ensure you don't have an antivirus or a firewall blocking communications.Using ZScaler ? Download the ZScaler certificate and import it into Conduktor.If you're using a VPN, you may have to configure it to not alter communication to *.conduktor.io or add a certificate into Conduktor (if you VPN adds its own security layer with a self-signed certificate.).The last step of our identification flow is a call to a local temporary http server ( so if something in the browser forces a redirect from http to https, the flow will never complete. Browser plugins can redirect http calls to httpS.You may need to add a trusted certificate to Conduktor:.Are you running Conduktor from your enterprise network?.That means that something is either preventing Conduktor to contact our authentication server ( ) or the other way around, something is preventing our authentication server to contact Conduktor Desktop on your computer (outside of our control) to finish the identification flow. When you login, you can stumbled upon this error in your browser. If you are running behind a VPN, your VPN client may prevent such connection, please look at its options. You probably have a networking tool on your system preventing this connection.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |