Using the Response Cookie authenticator

Many websites make use of an initial authentication method to create a user session, and then make use of session cookies to authenticate the user for subsequent requests. This authenticator uses a previously defined HTTP Client elsewhere in your station as the source of the session cookie. It searches the last response received on the source client for the cookie, or any Cookie Capture component added to the source client.
Prerequisites: You are working in . Workbench and are connected to the station with an HttpClientNetwork. The httpClient palette is open.
  1. Set up an initial request that authenticates the user.
    For this example, set up a station with SCRAM-SHA authentication to a station url.
    Image
    This creates a session.
  2. Drag a second HttpClient from the palette to the station and expand its Authenticator slot.
    The Authenticator properties expand.Image
  3. Change Auth Type to ResponseCookieAuth and click Save.
    The driver updates the Config options.
  4. Pick the Client to use to create the session, define the Cookie Name and click Save.
  5. Right-click HttpClient and click Actions > Send.
    The second client is able to access a protected url using the session cookie.
    Image
     NOTE: The Response Trigger and Response Chain components are useful if you need the first request to specifically trigger the Send action on a second.