There is this new option in Obsidian settings, called “Keychain”, but I have basically no idea how to use it or what’s it for. I tried searching this forum, Obsidian docs, even Google, but I get either some developer-related stuff, or links to stores with keychains. Can someone give me a link to docs or tutorial how to use it? AFAIU I should be able to store there some secrets, like a password I use in a plugin.
https://www.reddit.com/r/ObsidianMD/comments/1qkpt90/obsidian_keychain_native/
It’s a way for plugin developers to store API keys and other tokens. It’s brand new so it will take a bit of time for plugins to adopt it.
1 Like
I’m an Obsidian user, not developer. What use is your link to me?
ok so basically there is nothing I can do until plugin dev implements this in their plugin, and that’s the case for every and each plugin I use, right?
I thought I could define some environment variables and then directly use placeholders to replace the keys in all plugins.
But currently, it seems that you have to wait for each plugin to adapt one by one, which is not as convenient.
As a developer, I’d even go one step further. It is not just inconvenient: Switching out old setting fields (saved in vault folder) with the new component fields (saved in local cache) would break setups for all users who sync plugin settings across multiple devices.
Because it does not work with placeholders or env vars as commonly seen elsewhere, plugin devs will have to implement some sort of workaround, like presenting two fields for each value to allow users to either manually add text as before or linking a secret. All depending on the user’s use case which the plugin dev cannot (or at least should not) decide on.