When I was working with Azure Queue Service years ago, the way for my service to get delegated read-only access to a queue was: 1. My service's users would hav

When I was working with Azure Queue Service years ago, the way for my service to get delegated read-only access to a queue was: 1. My service's users would have to grant my service permission to read all access keys for the queue 2. My service would look through the access keys and try to find one matching some conditions (specific provided name and read-only) 3. If it couldn't find a limited one (which it would not in pretty much every real case due to the defaults) it would grab any read/write key and use that (Later, we used Managed Identity when that became available, which avoids the song-and-dance but also has performance issues with very large scale sets. Out of the frying pan...) I'm wondering if Jupyter had similar ability to read the primary r/w key for every database that had it enabled.