Doc Feedback: Mutual SSL Postman Testing Needs Update
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Postman images no longer match the current version of postman.
Option 1: Can we migrate this to curl examples instead?
Example:
TOKEN=eyJ4NXQiOiJPREUzWTJaa...
curl -vk https://mydomain.com:8243/pizzashack/1.0.0/menu
--cert ./demo.com.crt
--key ./demo.com.key
-H "Accept: application/json"
-H "Authorization: Bearer $TOKEN"
Option 2: Update postman images to match https://learning.postman.com/docs/sending-requests/authorization/certificates/
Option 3: Point users to postman documentation directly. (Option 2 link)
Option 4: Provide both curl and postman options
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked mutual SSL page and inspect the “Invoke an API Secured with Mutual SSL Using Postman” section; compare its steps and images with the linked Postman certificate documentation. Confirm which of the four proposed options is wanted, then update that section and verify the example or images match the selected approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postman
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100