I've been having some struggles with authentication for some services while getting started with ironclaw, and it's not well documented how users are intended to manage their secrets. Understandably, authentication patterns may drift over time, and so I understand why this might be the case. However, getting stuck and needing to reset things in order to overwrite credentials while trying different workarounds has proven to be quite the headache.
In short, if all of the secrets are intended to be stored in the user's database, I'm curious how much interest there is in a CLI tool or TUI integration to manually access and edit these credentials, or if there's an existing utility that I am missing. I think this would provide 2 major benefits:
(1) Custom credentials can be manually added / removed from the database for various purposes
(2) Provides clarity around what standard credentials are named and where they live for development purposes
I'm open to refinement on this concept or contributing to an existing feature plan, but I did not find anything on this front in the issues section or current documentation so far.
Related:
#2481
I've been having some struggles with authentication for some services while getting started with ironclaw, and it's not well documented how users are intended to manage their secrets. Understandably, authentication patterns may drift over time, and so I understand why this might be the case. However, getting stuck and needing to reset things in order to overwrite credentials while trying different workarounds has proven to be quite the headache.
In short, if all of the secrets are intended to be stored in the user's database, I'm curious how much interest there is in a CLI tool or TUI integration to manually access and edit these credentials, or if there's an existing utility that I am missing. I think this would provide 2 major benefits:
(1) Custom credentials can be manually added / removed from the database for various purposes
(2) Provides clarity around what standard credentials are named and where they live for development purposes
I'm open to refinement on this concept or contributing to an existing feature plan, but I did not find anything on this front in the issues section or current documentation so far.
Related:
#2481