cloudfoundry / cloudfoundry/uaa-cli
uaa curl assumes host
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22
- Forks
- 14
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Uaa curl does not work with any host but the targeted UAA.
uaac curl https://not-uaa-host.example.com is handy with workflows where you use uaa to grab a bearer token and then issue curl requests that utilize that token. For example https://docs.pivotal.io/platform/healthwatch/1-8/api/free-chunks.html#get
Here's a sample that doesn't work so well
$ uaa curl https://healthwatch-api.sys.example.com/v1/info -v
GET /https:/healthwatch-api.sys.example.com/v1/info HTTP/1.1
Host: login.sys.example.com
Authorization: Bearer abcd
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
Start from the uaac curl command entry point and reproduce the request shown in the issue with a non-UAA host. Trace how the target URL is converted into the request path and Host header; done means the full external URL is requested while the bearer token is still supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100