Enhancement: Authentication is currently only via user/pass, request API Client, too

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
api, authentication, cli

Research direction

The issue names no files, tests, or entry points. Start by locating the current user@customer:password authentication and header-matching flow, then trace how command requests are assembled; done requires a decided scope for OAuth bearer-token support and API Client authentication, with tests covering the accepted headers and token flow.

Written by the indexing model from the issue text.

Description

Currently, access is stored as user@customer:password, and calls with header values to match.

API Clients requires the header to pass bearer values, using access tokens obtained via OAuth.

Dominant language
Shell
Stars
46
Forks
41
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Appdynamics/api-commandline-tool

All issues in Appdynamics/api-commandline-tool

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.