Internal error from bws CLI when making frequent requests

Ask the Community Secrets Manager
1

If I make more than 10 requests, approximately 3 seconds or fewer apart, the 11th onwards will fail with the following error:

Error:
   0: Internal error: Failed to parse IdentityTokenResponse

Location:
   crates/bws/src/main.rs:172

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

After 20 seconds or so, it will work again.

At a guess, some sort of poorly handled rate limit? Anyone else seeing this?

1 Like
2

Thanks, the team is tracking this one.

1 Like
3

The above error seems to be fixed. I’m seeing a new error today:

Error: 
   0: Received error message from server: [404 Not Found] 

Location:
   crates/bws/src/main.rs:212
4

They had an outage this morning, but it’s resolved now, as you’ve likely noticed :smile:

The original issue isn’t fixed, though, to be clear. This simply masked it as Secrets Manager itself was down.

5

Is there any update on this? My primary use case for this is Ansible, and I wrote a simple PoC Ansible lookup plugin for bws, but this bug makes it unusable for anything more than a very minimal number of secrets.

6

Bump :slight_smile: I’d love to start making greater use of bws so I can properly evaluate it and potentially start integrating it into our workflows at work, but this issue is a real blocker for me.

7

@bw-admin sorry to keep pushing, I know these things take time, but is there any update? Not after an immediate fix, it would just be nice to know where the team is on this one.

Has the team acknowledged the issue?
Is it a deliberate rate limit?
Will the rate limit be increased if deliberate//resolved if not?

8

Hi @rafspeik thanks for following up and for your patience, the team is tracking the fix for this one, but no ETA at this time.

9

Thanks, I appreciate the update!

I just updated to the latest BWS CLI release (0.3.0) and it seems the error has been updated at least:

Error:
   0: Received error message from server: [429 Too Many Requests] {"message":"Slow down! Too many requests. Try again in 1m.","validationErrors":null,"exceptionMessage":null,"exceptionStackTrace":null,"innerExceptionMessage":null,"object":"error"}

Location:
   crates/bws/src/main.rs:307

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

That said, this response is clearly server-side, so my update to the latest client is likely immaterial.

As you mentioned that the team is working on a fix for this, I’m assuming that this rate limit was not supposed to be configured so low, and the fix will be to implement an increased rate limit?

10

Wondering if there’s any update on this issue now that Secrets Manager is generally available?

11

@rafspeik - has this issue been resolved?

12

Hi @bw-admin ! Is there any update on this?

13

any update?
ansible lookup hardly usable with 4 or more host because of this.

1 Like
14

Rate limits have been somewhat improved, but they are still both too low, IMO, and entirely undocumented.

For a developer-focused product, I find this to be pretty lacklustre at best. I really hope Bitwarden reconsiders this as I really like BWS, but this is a very frustrating problem, and I’m sure many people will be less patient than I when faced with such a problem.

15

I’ve been using bws-cache for Ansible lookups. It’s quite unfortunate that this is necessary, and it may well not fit all use cases, but it has helped to alleviate the issue.