Now that token authentication works everywhere1, it would be simpler and less confusing to remove the "Token auth or API Key" choice in the new credential flow and just default to token. We have heard that customers are sometimes confused by the choice and think we don't support token auth, even though it is present as a choice and just works.
We need to continue to support API Key credentials that already exist.
We may want to consider having some way to still make a new API Key credential as a fallback in case somebody finds a situation where Token auth is not working. Maybe a separate command they can invoke from the command palette?
Now that token authentication works everywhere1, it would be simpler and less confusing to remove the "Token auth or API Key" choice in the new credential flow and just default to token. We have heard that customers are sometimes confused by the choice and think we don't support token auth, even though it is present as a choice and just works.
We need to continue to support API Key credentials that already exist.
We may want to consider having some way to still make a new API Key credential as a fallback in case somebody finds a situation where Token auth is not working. Maybe a separate command they can invoke from the command palette?
Footnotes
We think. Verify that this is true! Search for open issues. We have tested and proved it works in Snowflake and Workbench. Try it with a proxy setup. ↩