search

postmanlabs / postman-chrome-interceptor

Helper extension for the Postman packaged app. Also helps send restricted headers.
Apache License 2.0
215 stars 75 forks source link

Unable to capture Authentication Cookies. #79

Open Swapnil-getpostman opened 4 years ago

Swapnil-getpostman commented 4 years ago

Describe the bug Unable to capture the authentication cookies in Postman application. [Application is connected to interceptor using the bridge.]

To Reproduce Steps to reproduce the behavior:

  1. Hit an endpoint for example - https://twitter.com (without login) and hit send button. As it will not get the authentication cookies. Reason it's not login to twitter.
  2. Login to your Twitter account. And hit the twitter endpoint again. Now it should get the authentication cookies because there is a successful login to the twitter account. But it's not getting the authentication cookies.

Expected behavior It should store authentication cookies in the postman application.

abhijitkane commented 4 years ago

@Swapnil-getpostman Is "twitter.com" added to the list of domains to sync cookies for?

Swapnil-getpostman commented 4 years ago

@abhijitkane Twitter is just an example here. User has added the domain - ibmcloud.com

abhijitkane commented 4 years ago

From the screen recording on the internal ticket, I see that the authentication cookies are showing up in Postman. There might be another way the server is determining auth status, or there might be a cookie on a root domain.

I'd recommend adding ibmcloud.com to the domain list, instead of a specific subdomain. Also, the user should check if there are any cookies in Chrome that have not been synced to Postman.