Hey lent — I'll look into this and let
Hey lent — I'll look into this and let you know what I find out.
6 Replies
I'm unable to recreate, it's working as expected for me, if I delete a key it no longer works. What steps did you use to delete the key?
Hi Brandon. Thank you for your help. @Brandon
On the My Profile page I clicked ... button next to it and clicked delete.
On the My Profile>API Tokens page I see no tokens listed.
From the dashboard going under Manage Account>AccountAPI Tokens I see no tokens listed. However I can confirm the key still works.
I am not able to reproduce it either. But I am able to show I have no keys in the UI, the key still works, and I am able to prove the key still works by querying my D1 database and getting results.
any chance you are using the global api key? could you re-roll/change it and see if you can still successfully query your db?
Yeah. I just rolled them and it is still working. I scoped the api token to only have D1 access and trying to do something else still fails. So that part is still being enforced.
Is it helpful if I share my account ID?
When you say it's still working do you mean you are creating a new instance and it is able to call d1 using that api key (via fetch and not the service binding).
For the record step results are cached. So it might look like it's working when it's now.
This is how I am testing "working" if I create a new table in the database through the dashboard Ui and run this code I see the new table.
Thank you again for your help!
Since I cant reproduce the issue with another token I am fine just wiping every trace of this key from my project and then forgetting about it, I just wanted to understand the issue since as far as I can tell this should not be happening.