[JBoss JIRA] Created: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
12:30 a.m.
It is not possible to use different credentials on the input of the service and on the
SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials set
to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:30 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/jira/browse/JBESB-3022?page=com.atlassian.jira.plu...
]
Jiri Pechanec updated JBESB-3022:
---------------------------------
Attachment: soapproxy-diffauth.zip
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:12 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/jira/browse/JBESB-3022?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-3022:
--------------------------------
Issue Type: Feature Request (was: Bug)
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:12 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/jira/browse/JBESB-3022?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3022:
-------------------------------------
Sorry, are you expecting a proxy to override the authentication? The purpose of the proxy
is to do just that, proxy the contents through to the endpoint.
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:35 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/jira/browse/JBESB-3022?page=com.atlassian.jira.plu...
]
Jiri Pechanec commented on JBESB-3022:
--------------------------------------
I believe it is a valid use case. The proxied WS can be 3rd party web service to which I
do not want to publicize credentials but instead of it I will mange the user access
myself.
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/jira/browse/JBESB-3022?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3022:
-------------------------------------
I agree that it is a valid use case and it can be simply handled by adding an action into
the pipeline to modify the details.
The current proxy work is intended to do just that, proxy the contents through. We can
certainly look at extending the functionality though.
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/jira/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:51 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin.s...
]
Keith Babo commented on JBESB-3022:
-----------------------------------
Running with Kevin's suggestion here. I have updated your project to include a
RemoveAuthHeader action in the action chain that demonstrates how existing HTTP auth
information can be removed. I tested this with your scenario where source and target have
same auth configuration but the HttpClient configuration specifies incorrect credentials
as an override. This fails as expected with the RemoveAuthHeader action in the chain. I
then tested a scenario where the source and target have different auth configuration and
used the HttpClient configuration to specify the different user/pass for the target web
service. This passed as expected with the RemoveAuthHeader action in the chain.
See attachment (wsp_diffauth2.zip).
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:53 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://jira.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin.s...
]
Keith Babo updated JBESB-3022:
------------------------------
Attachment: wsp_diffauth2.zip
Updated qs project with RemoveAuthHeader action.
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://jira.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip, wsp_diffauth2.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://issues.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3022:
-------------------------------------------
Bugzilla Update: Perform
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://issues.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip, wsp_diffauth2.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://issues.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3022:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=779281
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://issues.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip, wsp_diffauth2.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://issues.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-3022:
----------------------------------
Fix Version/s: 4.11
Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=779281)
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://issues.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Fix For: 4.11
Attachments: soapproxy-diffauth.zip, wsp_diffauth2.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:17 p.m.
New subject: [JBoss JIRA] (JBESB-3022) It is not possible to use different credentials on the input of the service and on the SOAPProxy that invokes the proxied service
[
https://issues.jboss.org/browse/JBESB-3022?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-3022:
----------------------------------
Fix Version/s: (was: 4.11)
It is not possible to use different credentials on the input of the
service and on the SOAPProxy that invokes the proxied service
---------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-3022
URL: https://issues.jboss.org/browse/JBESB-3022
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: Jiri Pechanec
Attachments: soapproxy-diffauth.zip, wsp_diffauth2.zip
There is a use case - I have a secured ESB service using HTTPS/BASIC auth invoking
invoking secured HTTPS/BASIC auth web service via SOAPProxy. If the credentials are passed
from the client then everything works correctly. But if I have different credentials
required for ESB client and different credentials are required by proxied Web Service then
I use property <property name="clientCredentialsRequired"
value="false" /> to set static credentials for proxied web service.
This property works correctly if the ESB service is unsecured. Unfortunately if it is
secured then probably the credentials stored in HTTP header stored in ESB message
overwrites the static credentials set by the SOAPProxy action.
The attached example is modified webservice_proxy_secure QS and has static credentials
set to wrong values - so proxied web service should not be invoked. But if ant runtest is
executed then the wrong credentials are not used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4468
days inactive
5267
days old
11 comments
5 participants
participants (5)
-
Jiri Pechanec (JIRA) -
Keith Babo (JIRA)
-
Kevin Conner (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Tom Cunningham (JIRA)