cl_http_client pass authorization token in request header

[vamsixk]

My problem is that the URL i want to use needs an Authorization header.

Authorization Bearer<Accesstoken>.

i have the access token with me. But when i configure the URL in an RFC destination with the Logon procedure as no Logon, it still asks for a Logon ID and Password when the request is called using cl_http_client.

I have used the propertytype_no_logon_popup but it does not suppress the logon popup.

but whenever i call with create_by_destination the popup is always triggerred.

we cannot use the create_by_url option because, we do not want to hardcode the URL.

Is there any way to configure the RFC destination so that, it does not trigger the popup and just uses the Authorization header?

[vamsixk]

I fixed this issue by using the method create_by_url instead of create by destination.

we used a workaround to store the URL in an RFC destination and build it dynamically, by fetching the details from the RFC destination instead of hardcoding it.

[Former Member]

Hi Vamsi,

i have got the same business requirement as you mentioned.

kindly can u let us know, complete solution steps for the above requirement asap.

Regards,

Manjunath