b0otable

[charred grove]

The CLI will create and use a restricted key (rk_xxx) on the account you authenticate with via stripe login

[west pasture]

I'm getting the error that it's using an expired test key, but when i look in google secret manager it looks correct

[charred grove]

Otherwise you can provide keys manually: https://stripe.com/docs/cli/api_keys

[charred grove]

I'd probably just do stripe login again to re-authenticate and trigger a new key

[west pasture]

I definetly don't want to trigger a new key... it is a huge pain to setup with Firebase and Google and Env's

[charred grove]

Confused how Google Secret Manager is relevant here? If you look at the CLI config it will show the keys it's using: https://stripe.com/docs/cli/config

You can manually set/unset them if they're wrong

[west pasture]

Manually specifing the key didn't work:

  "error": {
    "message": "The provided key 'rk_test_*********************************************************************************************qXj3rx' does not have the required permissions for this endpoint on account 'acct_******'. Having the 'rak_stripecli_session_write' permission would allow this request to continue.",
    "request_log_url": "https://dashboard.stripe.com/test/logs/req_bskRusg2RKwtn5?t=1689669549",
    "type": "invalid_request_error"
  }

I'm using the Firebase Stripe Extension

[charred grove]

Hmm, did you give the rk_xxx the CLI permissions? Looks like it's missing

[west pasture]

Hmm, does the CLI create its own keys separate (or in addition) to the keys created via the Stripe Developers section on the website?

I don't mind if the CLI creates its own test keys if I reauthenticate, I just can't have it replace the current restricted key that I have defined in 'Developers' -> 'Restricted keys'

[charred grove]

The CLI will generate keys on your account when you do stripe login yes. But they expire, which is what I guess happened here. The fix is to just stripe login again, but you don't want to do that

You can have multiple rk_xxx

[west pasture]

As long as it is just adding a new rk, I'm fine with that

[charred grove]

So maybe the CLI has one, and then your integration uses another

[west pasture]

Yes that is the case

I think because it expired I thought it was trying to share the current restricted_key

but I think you're right, the firebase extension is using one and the CLI was using a different one that expired

reauthenticate and hopefull that works

It worked @charred grove ! Thanks