Weirdness writing to storage

iPaaS Core Storages
1

Hello everyone,

Currently i am in the process of connecting a new (to us) api to Alumio. this api uses some hybrid form of oauth and basic auth to connect so the standard http authentications weren’t a proper fit. I thought i could solve this by using the bearertoken from storage auth which works as advertised when manually saving the bearerToken which i got via Postman.

However getting the bearerToken into the storage from an entity transformer gives me some trouble. The response that i get looks like this:

{
    "access_token": "TestTokenInformationThatiShouldStore",
    "expires_in": 3600,
    "token_type": "Bearer"
}

When i have set the source of the “save entity to storage” set to &{access_token} it write a null to the storage. How would i go and only store “TestTokenInformationThatiShouldStore” ?

scratch that i just figured it out XD. turns out i shouldn’t use the placeholders while the ui says i should

afbeelding
afbeelding1331×130 4.99 KB

2

@jesse.wever the ‘supports placeholders’ indication actually means that it can take the value of a placeholder as key to use as pointer for the source.

I.e. if the authentication request would contain an extra value such as ‘token_field’ with value ‘access_token’, you could use &{token_field} which would trigger Alumio to find the ‘access_token’ field and use that value as it’s source.

3

ahh, then it makes sense it wouldn’t work. thanks for the information