Set and Pass Mulesoft client id and client secret in Proxy call

Question

Hello members,

We have a requirement, where we need to route FE - Mulesoft calls via AEM Dispatcher. So, we are using Dispatcher rewrites 301 Redirect to pass FE request (which is AEM SPA components only) to Mule system.

Now, we need to set Mule client id and client secret in incoming request and redirect to Mule system from Dispatcher.

Any pointers would be helpful and sample code example will be add on 🙂

Thanks!

cc: @aanchal-sikka @tanika02

yuriy_shestakov · Accepted Answer

Thanks @yuriy_shestakov for pointers.So, I am trying to do that using rewrite rule to send request to Mule server. I need to set RequestHeader with client_id and client_secret. How can I do that?cc: @arunpatidar I've never done something like that. Only updated once request/response headers for the current request, not for remote.Does it work with rewrite rules? I thought there must be a path on the same server, not a remote address. Or do you use some Apache module, like mod_proxy?To update response headers I used this one: Header always set CLIENT_ID ${CLIENT_ID} but it will update the headers that you send to the client. For the request it will be `RequestHeader set`, but I don't know if it works if you put it before RewriteRule. Update: found a sample on Stackoverflow, you can try using directive. Header set MULE_CLIENT_ID "clientId"...RewriteRule ^/api/mule/(.*)$ https://mule.website/$1 [P]

viveksachdeva · Answer

301 redirects are cached by browsers, so these requests wouldn't even go to dispatcher once cached in browser. Any reason you are trying to do 301?

And I assume you want to pass client id and secret in headers?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded