aws / aws/amazon-q-developer-cli

Fallback to Client_id and secret flow if OAuth flow doesn't support Dynamic Client Registration (DCR)

Open
#2,982 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.6.1 (24G90)

### Expected behaviour

If an authorization server doesn't support DCR, Q CLI should fallback to using client_id and client_secret to complete OAuth Flow

### Actual behaviour

Authorization URL returned as part of OAuth flow is invalid

### Steps to reproduce

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.