You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to re-open #11. As a first iteration, graphql-mode could read ~/.authinfo prior to sending a request, check if there is a mapping for the host in question, and if so set the HTTP header Authorization using the basic access authentication as specified by RFC 7617: The 'Basic' HTTP Authentication Scheme.
The text was updated successfully, but these errors were encountered:
Are there any other modes with the same needs?
Just looking at my own .authinfo I can see that I'm using it for accessing a JIRA board. I forget which package implements this, though. I'm also using magit/magit-forge to access various Git "forges".
As for security concerns, a user can use .authinfo.gpg as an alternative. That file is expected to be encrypted. Of course storing passwords in clear-text files may pose security concerns in some cases.
I don't have a lot more details, because I don't really know how it's implemented. It's always easier just to ask for features than to put in the work ;)
I can't promise I'll dedicate time for this, but if you have pointers that could be useful for implementing this, please do share.
I'd like to re-open #11. As a first iteration,
graphql-mode
could read~/.authinfo
prior to sending a request, check if there is a mapping for the host in question, and if so set the HTTP headerAuthorization
using the basic access authentication as specified by RFC 7617: The 'Basic' HTTP Authentication Scheme.The text was updated successfully, but these errors were encountered: