So I've been using SoapUI for just a day. My business decided it would be a good tool to use for our Rest service API's we've developed. The tool seems quite in depth and I haven't figured everything out just yet, so I do apologize if the solution to my issue is simple and/or mundane.I've created two Rest resources. One that grabs two important authentication variables and one that passes the authentication variables along with the request. But I've only gotten this working when I statically set this. Our authentication tokens reset daily, so I'm looking for a way to run the token method, and then pass the two variables to the next action method.I have successfully figured out how to use the PropertyTransfer tool, but I can not seem to figure out how to concatenate the two values into one, and then pass that in along with the URL for the following action.To give a very general idea, here's a quick breakdown:TokenRequest -> returns token_type="bearer" and access_token: "random large string".RequestMethod -> sends token_type + " " + access_token + " " request_stringI have not figured out how to concatenate the token_type and access_token into one authorization variable.Any advice/help is certainly appreciate.

RamboMadCow Here's what I've done Create a step that goes out and gets your token. Name it "get_token"Create the next step as a groovy script, and name it "xfer_bearer_token". In the script area, you can right click>GetData>... then point it at the previous step's response/property. This will prompt you create a variable in the groovy code. Then just return your concatenation like this Create a step that calls an endpoint that needs the token. Set up a property in this step called 'Authorization' and set the style to 'HEADER'. Right click inside of the property value>GetData>... then find your groovy script that you just made. Choose the result of the groovy script This worked for me

Custom properties at the project level can be dynamic using a property transfer test step.or property expansion. https://support.smartbear.com/readyapi/docs/soapui/steps/property-transfer.html Property transfer maybe easier. https://support.smartbear.com/readyapi/docs/testing/properties/expansion.html Property Expansion | ReadyAPI Documentation To refer to properties in other test suites or test cases, use the full "path" to specify the desired scope. The "path" part is enclosed in square brackets. ${#[Suite name#Case name#Step name]#Property name} Example The value for project property IdentifierValue could be set to ${#[Suite name#Case name#Step name]#Response#$..Id[0]} even though Get Data dialog is not available.

It is possible to concatenate the token_type and access_token without adding a groovy script step. Using this example add header style parameter Name: Authorization Value: ${get_token#Response#$.token_type} ${get_token#Response#$.access_token} or if the type is always bearer Value: Bearer ${get_token#Response#$.access_token} An advantage of using groovy script step is that if you need to use the same authorization header for many requests then property expansion to get data from the response is only processed once and will be consistent.

HI there, could you please let me know what step we need to use in below step to get auth token. Create a step that goes out and gets your token. Name it "get_token"

Hi, You can use property expansion instead of property transfer. I recommend you watch this video that will show you how to use the right-click -> Get Data... functionality in SoapUI Pro to generate the property expansion needed to add the needed data to your request: http://www.soapui.org/Working-with-soapUI/point-and-click-testing.htmlRegards, GiscardSmartBear Software

Passing a dynamic authentication token

dasjestyr
New Contributor
10 years ago
RamboMadCow

Here's what I've done

Create a step that goes out and gets your token. Name it "get_token"
Create the next step as a groovy script, and name it "xfer_bearer_token". In the script area, you can right click>GetData>... then point it at the previous step's response/property. This will prompt you create a variable in the groovy code. Then just return your concatenation like this
Create a step that calls an endpoint that needs the token. Set up a property in this step called 'Authorization' and set the style to 'HEADER'. Right click inside of the property value>GetData>... then find your groovy script that you just made. Choose the result of the groovy script

This worked for me
- NamrataMane
  Occasional Contributor
  8 years ago
  HI there,
  
  could you please let me know what step we need to use in below step to get auth token.
  
  Create a step that goes out and gets your token. Name it "get_token"
  - nmrao
    Champion Level 2
    8 years ago
    NamrataMane,
    Suggested you to create a new question with details so that some one can understand the issue better. Use screen shot if required.
- Crazy_Chris
  Occasional Contributor
  8 years ago
  Hi dasjestyrm,
  
  Although this is somewhat late, I would like to thank you for the proposed solution.
  This was just was I was after! Simple, short and to the point :)
  
  To Smartbear:
  Although I have to say that it seems unnecessary difficult to achieve this. Why can't I use get data to the element in another test and extract the fields that way without going through (although rather simple and short) groovy script to define new values and then use Get Data that is somehow able to extract the same information I wanted in the first place...
  This makes zero sense from a user perspective, why are headers and ressources excluded or limited with what data can be retrieved? It's obviously there, or it would be impossible even through a groovy script.
  - PaulMS
    Super Contributor
    8 years ago
    It is possible to concatenate the token_type and access_token without adding a groovy script step.
    
    Using this example add header style parameter
    
    Name: Authorization
    
    Value: ${get_token#Response#$.token_type} ${get_token#Response#$.access_token}
    
    or if the type is always bearer
    
    Value: Bearer ${get_token#Response#$.access_token}
    
    An advantage of using groovy script step is that if you need to use the same authorization header for many requests then property expansion to get data from the response is only processed once and will be consistent.
SmartBear_Suppo
Alumni
11 years ago
Hi,

You can use property expansion instead of property transfer.
I recommend you watch this video that will show you how to use the right-click -> Get Data... functionality in SoapUI Pro to generate the property expansion needed to add the needed data to your request: http://www.soapui.org/Working-with-soapUI/point-and-click-testing.html

Regards,

Giscard
SmartBear Software
- dasjestyr
  New Contributor
  10 years ago
  I don't think this answered the question. The video shows GetData... as being pretty much the same functionality as Transferring a property. What the OP asked is how he can append something to the beginning of the property being copied.
  
  For each, if you have a test that goes off to a service to retrieve a token, and it gets returned in the response as "ABCD1234", he needs to transfer it to a property (maybe a header) as "Bearer ABCD1234" but there doesn't seem to be any clear way to do something like this except maybe a groovy script? Either way, I don't think you answered the question. Could you please clarify?

Forum Discussion

Passing a dynamic authentication token

Recent Discussions

Windows installation <user>

Automation for SignalingService

Unable to see receive MQTT message in response

Related Content

Kafka topic using OAuth2 authentication

Identifying Dynamic message window

ReadyAPI Authentication