[
https://issues.jboss.org/browse/JBIDE-15830?page=com.atlassian.jira.plugi...
]
Brenton Leanhardt commented on JBIDE-15830:
-------------------------------------------
I definitely think the jenkins-plugin should be setting the user-agent instead of relying
on the default behavior of the openshift-java-client. For what it's worth, when I
performed a packet capture of the jenkins-plugin compiled with 2.4.0-SNAPSHOT or later of
openshift-java-client the user-agent was set to "Java/1.7.0_45".
I see in
https://github.com/openshift/jenkins-cloud-plugin/blob/master/src/main/ja...
that the OpenShiftConnectionFactory is being used. I'm guessing that's probably
where the user-agent should be passed in.
As for the openshift jenkins plugin itself, there is a story upstream to deal with a large
chunk of technical debt that includes creating tests that actually work and do something
useful.
openshift-java-client: incompatibility with OpenShift Enterprise and
Origin when using the remote-user authentication plugin
----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-15830
URL:
https://issues.jboss.org/browse/JBIDE-15830
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Brenton Leanhardt
Assignee: Andre Dietisheim
Labels: openshift-java-client
Fix For: 4.1.1.CR1, 4.2.0.Alpha1
OpenShift Enterprise and Origin both ship an authentication plugin that allows parts of
authentication to be handled by Apache and other parts to be delegated to the
openshift-origin-controller codebase. I've found that all versions of
openshift-java-client after 2.3.0.Final change a (poorly documented) requirement for the
OpenShift remote-user plugin.
In order for a request to bypass the Apache authentication and passthrough to the
OpenShift Broker the user-agent header is inspected. If the user-agent is
'OpenShift' then the Broker will require an encrypted authentication token. Today
this is used by the jenkins cartridge but I believe it's also still used for scaling.
You can see this for details:
https://github.com/openshift/origin-server/blob/master/documentation/arch...
In 2.3.0.Final of the openshift-java-client the user-agent was 'OpenShift'
however all versions after this set the user-agent to the java version (eg, User-Agent:
Java/1.7.0_45).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira