cloudfoundry / cloudfoundry/uaa-cli
`uaa help` expects too much knowledge
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22
- Forks
- 14
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
I want to log in to the UAA used by my cloudfoundry to perform some basic user management.
Getting Tokens:
get-authcode-token Obtain an access token using the authorization_code grant type
get-client-credentials-token Obtain an access token using the client_credentials grant type
get-implicit-token Obtain an access token using the implicit grant type
get-password-token Obtain an access token using the password grant type
get-token-key View the key for validating UAA's JWT token signatures
get-token-keys View all keys the UAA has used to sign JWT tokens
refresh-token Obtain an access token using the refresh_token grant type
All of these descriptions expect a lot of context about UAA.
Is it possible to have a simple login flow instead, just like when I go to the UAA web interface?
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 by reviewing the uaa help command list and the existing token-related flows described in the issue. Determine how a browser-like login should fit the CLI and define the expected user interaction and completion criteria. The issue is old and names no files or tests, so repository exploration and maintainer guidance are needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100