I have a branding extension that allows me to change the icon and server name in the UI for the server. When I deploy an app to the server using the Run As> dialog, I see log messages of this type in the console :

Checking application - my-web-app
Generating application archive
Creating application in Cloud Foundry server
Pushing application to Cloud Foundry server
Application successfully pushed to Cloud Foundry server
Starting and staging application

I'd love to change this to
Checking application - my-web-app
Generating application archive
Creating application in server
Pushing application to server
Application successfully pushed to server
Starting and staging application

I'd like to submit a PR which adds another extension point to the branding plugin which takes in the company name or just uses the one passed in to the server type name.

See the following STS JIRA for details: https://issuetracker.springsource.com/browse/STS-4024

The fix that worked for me:

if (curOldValue != curNewValue) {
   if (/NEW/ curNewValue == null /NEW/ || !!! curNewValue instanceof IServerType) {
       if (isSupportedServerType((IServerType)curNewValue)) {
                        // Disable the host name field
                        if (controlListener != null) {

Chunk of code between /NEW/ has been added to account for null values that can be selected (folders)

I'm planning to contribute the removal of the stdout and stderr log files to the DEA soon.

cloudfoundry-attic/dea_ng#115

I hope that loggregator integration is high on your list. I want to get my developers to start using this plugin soon but viewing logs will be important.

When I try to login with a user I get the following error appears:

Unable to communicate with server - Could not read JSON: No content to map due to end-of-input at [Source: org.apache.http.conn.EofSensorInputStream@161e6025; line: 1, column: 2482]; nested exception is com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: org.apache.http.conn.EofSensorInputStream@161e6025; line: 1, column: 2482]

This is the response I get from my token endpoint, which is for the CF-CLI fully valid and works.

{"access_token":"eyJhbGciOiJSUzI1NiJ9...","token_type":"bearer","refresh_token":"eyJhbGciOiJSUiJ9...","expires_in":599,"scope":["password.write","cloud_controller.write","openid","cloud_controller.read"],"jti":"0eb132c2-f400-4b27-bfd5-8a0315284d2e","sub":"123321-1233-4353-8490-e1df73ef239c","client_id":"cf","cid":"cf","azp":"cf","grant_type":"password","user_id":"1234567-1234-2343-8490-e1df73ef239c","user_name":"username1","email":"[email protected]","iat":1427816165,"exp":1427816765,"iss":"https:\/\/uaa.xyx.ch\/oauth\/token","aud":["cf","password","cloud_controller","openid"]}

Thanks for you help
Dave

Here some more information:
Plugin version: 1.8.1 (A collegue of mine also tried this with version 1.8)
This happens when I try to login into a CF within the wizard of creating a new CF server.

The plugin is passing credentials directly to the UAA which is bypassing custom profiles like LDAP.

The new gcf client had the same issue: cloudfoundry/cli#29

-- Jon Price

App creation wizard expects to have a valid url in the buildpack field which is wrong behavior. Users should be able to specify a system or admin buildpack in this field.
If a manifest with a non-url buildpack name is present, the buildpack field is populated correctly and validation does not get triggered.

Starting position:
We have implemented an external authorization server (portal). So the portal provides the login information which also provides the prompts. The CF UAA functions for token handling only.

In the /login response from the portal asks for the following prompts: username, 2factor, password.

I have the same problem as here https://groups.google.com/a/cloudfoundry.org/forum/#!searchin/vcap-dev/eclipe/vcap-dev/btP9wybkg1E/uQd59Z8MPiAJ.

My questions: Are additional prompts properly handled?
After a lot of analyses I think this is the problem.

I've created a self-signed cert in Ops Manager. Validating server credentials using the admin account in version 1.81 of the plugin (in STS 3.5.1) results in an authentication error:

Unable to communicate with server - I/O error on GET request for "https://api.system.22x.edu.pivotal.io/info":sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Using the --skip-ssl-validation option on the CLI results in a successful login. For the record, I've downloaded version 1.73 of the plugin and it does successfully authenticate on validation.

When I drag and drop a web app onto the application & services window in a server's properties, the Deploy application wizard pops up twice.
The plugin version I'm using is :
Cloud Foundry Integration for Eclipse 1.7.0.201406182004-RELEASE

Here's a screenshot

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

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

When deleting a project that is mapped to a published Cloud module, prompt the user whether to delete the application or not.

This implementation could reuse the same replace method in CloudFoundryServer as used by the "Unmap Project" feature:

https://github.com/cloudfoundry/eclipse-integration-cloudfoundry/blob/5b85a860efffe62426dc12235a0d60e586f1fdb2/org.cloudfoundry.ide.eclipse.server.core/src/org/cloudfoundry/ide/eclipse/server/core/internal/CloudFoundryServer.java#L583

This was originally raised via a Pull Request from HuaweiTech:

#27

The following error message shows up in my workspace .log file when I installed only the CF integration (not the UAA plugins).

!ENTRY org.eclipse.wst.common.project.facet.core 4 0 2012-04-09 22:11:23.409
!MESSAGE Project facet grails.app has not been defined. It is used in plugin org.cloudfoundry.ide.eclipse.server.branding.

We are integrating the login-server with SAML. The eclipse plugins only support authentication using local UAA accounts (or I believe direct LDAP integration also).

The plugins should be able to call the /login endpoint and determine that SAML is enabled and present the OTP options.

Hi folks,
I'd like to understand how I can communicate that I'm fixing issues that are filed in the Pivotal tracker. For example, I'm working on a fix for this issue Add operation buttons to Env Variables wizard page., and before I send out the PR, I'd like to communicate that I'm working on this issue and maybe get the issue assigned to me in the Pivotal tracker. Am looking for the workflow of working between the tracker and github issues.

Deploy apps.
Configure the target as a Server.
Load the files in RS view.
Open a file in editor.
Relaunch IDE.
Delete sever.
Delete the Remote Systems connection.
Redeploy the app.
Add the server.
Reopen the Remote Systems view.
Reopen the file.
See old content.Invoke Refresh.
Still see old content.

If I use cf files app path command I see new content.

Disconnecting and connecting to server does not help.

This may be an RSE Issue.

CF Int for Eclipse version:
Cloud Foundry Integration for Eclipse
Version: 1.7.0.201406182004-RELEASE