Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicit 443 is not the same as implicit 443 when using client certificates #4707

abatishchev opened this issue Jun 15, 2018 · 6 comments


Copy link

@abatishchev abatishchev commented Jun 15, 2018

Describe the bug:

Port is treated literally when client certificate is chosen from settings

To Reproduce
Steps to reproduce the behavior:

  1. Go to Settings -> Certificates
  2. Add certificate for (specify 443 explicitly)
  3. Call (no 443)
  4. Observe error 401 Unauthorized
  5. Call
  6. Observe no error

Expected behavior

If port 443 was specified in settings then it's treated the same way if it was omitted.

App information (please complete the following information):

  • App Type: Native
  • Postman Version: 6.1.3 win32 10.0.17134 / x64
  • OS: Windows 10 x64 April Update
Copy link

@numaanashraf numaanashraf commented Jul 12, 2018

@abatishchev This is a verified bug. We are working on fixing this.

@harryi3t harryi3t assigned kamalaknn and unassigned harryi3t Jul 18, 2018
Copy link

@qcastel qcastel commented Aug 17, 2018

++1 on this one. We are using this feature for Open Banking, in the financial sector, and this bug is really affecting the user experience for our all community: We decided to use postman as a way of documenting/exploring the Open Banking standard, we really like to see this issue fixed soon.

Copy link

@pwcremin pwcremin commented Aug 22, 2018


Copy link

@benjefferies benjefferies commented Oct 10, 2018

Any updates on the fix @numaanashraf?

Copy link

@codenirvana codenirvana commented Mar 28, 2019

We've released a fix for this on our Canary (version: 7.1.0-canary01) channel

@abatishchev @qcastel @benjefferies Please try it out in the Canary version and let us know if you continue to face the issue.
Will update the thread once we release the fix on our stable channel.

Copy link

@codenirvana codenirvana commented Apr 23, 2019

This has been fixed in the latest Postman app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
10 participants