See https://www.openshift.com/forums/openshift/the-credentials-for-user-are-not-valid#comment-33837  

Upgrade to Kepler worked for me.

I just found out what breaks the openshift-java-client:
It's an addition to the REST responses that the library cannot handle. It stumbles upon the following:

<snip>
               {
                    "default_value" => undefined,
                    "description" => "Add or Update application environment variables, e.g.:[{'name':'FOO', 'value':'123'}, {'name':'BAR', 'value':'abc'}]",
                    "name" => "environment_variables",
                    "type" => "array",
                    "valid_options" => []
                }
</snip>

The error is caused by "type" => "array" which it doesnt know and complains. Clearly a shortcoming in the client library, something the client library should simply ignore. But I cannot go back and backport the correct behaviour know in latter versions.
Btw. This also break our existing JBDS6 users. IMHO we should consider removing this response from protocol 1.0 since it breaks existing users.

To track this issue in JBoss Tools/JBoss Developer Studio, I filed https://issues.jboss.org/browse/JBDS-2750 in our jira. 
Can you please add this as external bug-tracker? I cannot, seem not to have sufficient permissions.

We closed the JBDS issue and filed this to the JBoss Tools jira (since this is not specific to JBDS) at https://issues.jboss.org/browse/JBIDE-15396. Please add this as external bugtracker in this bugzilla (I cannot, I'm missing the priviledges)

Zend Studio 10 users are hitting the same problem with current OpenShift Online.

(https://issues.jboss.org/browse/JBIDE-15400 closed as duplicate of https://issues.jboss.org/browse/JBIDE-15396)

Zend confirmed they're going to update the openshift-java-client in the future Zend Studio 10 versions.

In my opinion, we should hotfix the REST issue described in comment 2.

*** Bug 1004083 has been marked as a duplicate of this bug. ***

Ravi pushed a fix https://github.com/openshift/origin-server/pull/3559

Test on STG(dev_stage_375), and work well, so verified this.

Reproduced with eclipse Juno & jboss tool for Juno on PROD;
Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD;
Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD;

(In reply to Nam Duong from comment #1)
> See
> https://www.openshift.com/forums/openshift/the-credentials-for-user-are-not-
> valid#comment-33837  
> 
> Upgrade to Kepler worked for me.

Ok I did and It works! Thanks.

Hi weiwei jiang

(In reply to weiwei jiang from comment #10)
> Reproduced with eclipse Juno & jboss tool for Juno on PROD;

expected, thanks for confirming.

> Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD;

completely unexpected and contradicts Nam telling upgrading worked for him. Are you sure that kepler + JBT 4.1. is NOT working for you?

> Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD;

expected, thanks for confirming (but is in contradiction to the above. JBDS7 == Kepler + JBT 4.1).

(In reply to weiwei jiang from comment #10)
> Reproduced with eclipse Juno & jboss tool for Juno on PROD;
> Reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD;
> Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD;

Update the result.

 Reproduced with eclipse Juno & jboss tool for Juno on PROD;
 Can not reproduced with eclipse kepler & jboss tool 4.1.0.final.core on PROD;
 Can not reproduced with Jboss Developer Studio 7.0.0.GA on PROD

I just verified JBDS6 (which is equivalent to JUNO + JBT 4.0) and it works for me on STG. awesome!
The links to the environment variables, which cause JUNO + JBT 4.0 to break are now gone.
I also verified Zent Studio 10 which works for me now when using (the fixed) https://stg.openshift.redhat.com