Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid API Key; Organization API Key currently not supported #11965

Open
1 task done
hinricht opened this issue Nov 12, 2024 · 3 comments
Open
1 task done

Invalid API Key; Organization API Key currently not supported #11965

hinricht opened this issue Nov 12, 2024 · 3 comments
Labels
bug cli CLI Application

Comments

@hinricht
Copy link

Steps To Reproduce

  1. Go to the web interface
  2. Click on Admin consle
  3. Click on Settings
  4. Click on Organization info
  5. Click on View API key
  6. Enter your master password
  7. Note down client_id and clienr_secret
  8. On the command line run bw login --apikey
  9. Enter client_id and clienr_secret

Expected Result

The login should succeed.

Actual Result

The login fails:

$ bw login --apikey
? client_id: organization.1...
? client_secret: ...
Invalid API Key; Organization API Key currently not supported

Screenshots or Videos

No response

Additional Context

No response

Operating System

Linux

Operating System Version

Manjaro sway edition (rolling release, latest patch level)

Shell

Zsh

Build Version

2024.8.0

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@hinricht hinricht added bug cli CLI Application labels Nov 12, 2024
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-14848

@hinricht
Copy link
Author

Our use case is to provision our Bitwarden organization with the Bitwarden Terraform provider. We don't want to tie any personal / account related API keys to the provisioning and therefore want to use the organization API key.

@rmcdowell-bitwarden
Copy link
Collaborator

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cli CLI Application
Projects
None yet
Development

No branches or pull requests

3 participants