New feature: Support API endpoints protected by kerberos
Postman doesn't seem to support authentication using **kerberos**, or more generally **HTTP Negotiate (SPNEGO)** mechanism. The equivalent way of authenticating using kerberos via `curl` is something like below: ``` shell $ kinit $ ... # enter password for user $ curl --negotiate -u : <api_endpoint> #200 OK ```
Posted by brijs on Aug 9, 2016, 6:09 PM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
New feature: Support API endpoints protected by kerberos
Postman doesn't seem to support authentication using **kerberos**, or more generally **HTTP Negotiate (SPNEGO)** mechanism. The equivalent way of authenticating using kerberos via `curl` is something like below: ``` shell $ kinit $ ... # enter password for user $ curl --negotiate -u : <api_endpoint> #200 OK ```
Comments (0)
No comments yet. Start the discussion.