IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Rest Request Web Service Bearer Token Options · View
stewhi019
Posted: Thursday, January 30, 2020 5:52:37 PM
Rank: Newbie

Joined: 1/30/2020
Posts: 4
Hello. I am still fairly new to MapForce and joined this forum after searching for a solution.

I am trying to use MapForce to retrieve data from a web service. To use this service, I must first obtain a bearer token (which I have done successfully in the application).

Would somebody please point me in the right direction for supplying a second call to another endpoint with this bearer token? I don't see anything in the settings for authorization other than username/password. I am sorry if I have missed a relevant topic, but I have searched without finding anything.


K101
Posted: Tuesday, February 11, 2020 1:44:19 PM
Rank: Advanced Member

Joined: 2/27/2009
Posts: 564
Are you passing this token in as a parameter? Is it something coming from yet another web service call, something that expires periodically or anything like that?
stewhi019
Posted: Thursday, February 20, 2020 3:15:02 PM
Rank: Newbie

Joined: 1/30/2020
Posts: 4

Yes, the token expires on a specified interval. I did figure it out and it was actually so simple. I guess that is why I was overlooking it.

I was taking the literal response token and plugging that into the new request. What was needed was just a concatenate ("Bearer ",{TOKEN}) to match the string the service is looking for exactly.

The service is doing pagination on the results so I have to figure that out next but in good shape now. Thank you!


stewhi019 attached the following image(s):
Bearer2020-02-20_9-10-19.jpg

stewhi019
Posted: Thursday, February 20, 2020 3:15:44 PM
Rank: Newbie

Joined: 1/30/2020
Posts: 4

Yes, the token expires on a specified interval. I did figure it out and it was actually so simple. I guess that is why I was overlooking it.

I was taking the literal response token and plugging that into the new request. What was needed was just a concatenate ("Bearer ",{TOKEN}) to match the string the service is looking for exactly.

The service is doing pagination on the results so I have to figure that out next but in good shape now. Thank you!

Users browsing this topic
guest

Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.