cloudfoundry-attic / eclipse-integration-cloudfoundry

Cloud Foundry Integration for Eclipse
Apache License 2.0
41 stars 47 forks source link

Unable to add NISE CF as a server in Eclipse via CF Plugin #6

Open kjhawar opened 10 years ago

kjhawar commented 10 years ago

I want add my private CF NISE cloud as a server in the Eclipse IDE via the CloudFoundry Plugin.

My CF NISE setup is on virtualbox.

Initially, there were SSL exceptions (due to expired hard coded certificate in the code base and incorrect CN). i replaced the certificates with CN = api.10.39.39.39.xip.io.

the URL provided is "https://api.10.39.39.39.xip.io". It needs email address and password to validate the account. i have tried admin/c1oudc0w and vagrant/vagrant but its unable to validate eclipse1

What credentials does this plugin expect for a CF NISE setup?

nierajsingh commented 10 years ago

Hi,

Thanks for raising the issue. Have you tried using the command line tool 'cf' to see if the issue is also reproducible there?

http://docs.cloudfoundry.org/devguide/installcf/

Do you get the same validation issues with the credentials that you specified through CF Eclipse?

Normally, CF Eclipse is no different than the cli or web interfaces in terms of validating credentials and logging into an account. A set of valid credentials should work in all three cases.

If you have a chance to try it out, it will help us narrow down the issue. Thank you.

kjhawar commented 10 years ago

Hi I can log in using CF CLI with credentials admin/c1oudc0w. I tried these credentials with the eclipse plugin but failed.

nierajsingh commented 10 years ago

Hi,

Thanks for trying out CF CLI.

The latest nightly build for CF Eclipse has additional error detection when validating credentials.

If possible, please try the following:

Update to the CF nightly build through the Eclipse Help -> Install New Software menu, and entering this URL:

http://dist.springsource.com/snapshot/TOOLS/cloudfoundry/nightly

Once installed and restarting Eclipse, please try revalidating the credentials and see if the New Server wizard displays additional errors.

Thanks.