Secoda Community

Hey Kiara, this is a bug on our end but there is a workaround if you don’t want to wait on us to fix the issue.

To get the session id you can follow these instructions:
1. Sign out of Metabase
2. Open up the Developer console (Right click and click “Inspect”)
3. Go the the “Network” tab and check the box for “Preserve log”
4. Login to Metabase
5. Go back to the Developer console and click the `google_auth` request. Go to the “Response” tab and copy the `id`
6. Go to Secoda and add the Metabase integration and instead of a password use a session token
Here’s a video demonstration as well <https://www.loom.com/share/fd3f422022b041a0a757045064a2a2d6>

it doesn’t seem to be working. I can wait for a fix - is there an estimated completion date for a fix on this?

I will get it out so it’s ready on Monday!