-
Notifications
You must be signed in to change notification settings - Fork 87
HttpSender
Jeroen Jansen van Rosendaal edited this page Sep 21, 2026
·
5 revisions
The following is a simple example configuration for using the HttpSender:
<Pipe name="LocalHttp">
<HttpSender
methodType="POST"
url="${web.protocol}://${web.host}:${web.port}${web.contextpath}/HttpListener?service=LocalHttpListener"
inputMessageParam="request"/>
<Forward name="success" path="EXIT" />
</Pipe>
The following is the implementation for wso2 using a bearertoken and resolving the credentials from a vault (for picking up the token) if you want to use a username passwrod to pick up the token delete clientAlias and use clientSecret(pw) and clientId(username):
<SenderPipe name="CallPostOnboarding"
storeResultInSessionKey="postOnboardingResults">
<HttpSender
allowSelfSignedCertificates="true"
authenticatedTokenRequest="true"
tokenExpiry="10000"
tokenEndpoint="${VarWSO2BaseUrl}/token?grant_type=client_credentials"
clientAlias="wso2_client"
headersParams="Accept"
urlParam="url"
methodType="Post"
timeout="36000"
resultStatusCodeSessionKey="resultCode"
maxExecuteRetries="3"/>
<Param name="url" sessionKey="postOnboardingUrl" />
<Param name="Accept" value="application/json" />
<Forward name="timeout" path="createLogMessageError" />
<Forward name="success" path="RouteCodeResult" />
<Forward name="exception" path="BackEndError" />
</SenderPipe>