[ https://issues.jboss.org/browse/JBDS-4677?page=com.atlassian.jira.plugin.... ] Roman Martin Gil commented on JBDS-4677: ---------------------------------------- I tested again using a local OCP cluster (oc cluster up --public-hostname=127.0.0.1) to compare with the real OCP cluster used. The results were the same I can't connect from JBDS. However I can do it from a browser or using oc command, but the first connection I got a warning to accept the certificates used by the cluster. The oc command results are: {code:java} [rmarting@kiuran jenkins]$ oc login -u developer -p developer https://127.0.0.1:8443 The server uses a certificate signed by an unknown authority. You can bypass the certificate check, but any data you send to the server could be intercepted by others. Use insecure connections? (y/n): y Login successful. You have access to the following projects and can switch between them with 'oc project <projectname>': * default kube-public kube-system myproject openshift openshift-infra openshift-node Using project "default". Welcome! See 'oc help' to get started. {code} Attached a screenshot when I used the browser the first time. !jbds-openshift-browser.png|thumbnail! It seems that OpenShift Wizard connection doesn't manage successfully the warning to accept the credentials from the OCP Cluster and after that I can't create the connection definition. I don't think it is something related with my TLS support. Could you reproduce it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)