Re: Potential bug/inconsistency in auth-source netrc vs plstore backends

[Xiyue Deng]

Soham Gumaste <sohamg2@gmail.com> writes:

>>
>> I think that's how auth-source is supposed to work.  People would need 2
>> entries with different `:port's, one for imap(s), one for smtp, for both to
>> work.  Or maybe there is a better way now?
>>
>
> Well, auth-source should also work if one has simply `password
> <password>` in the netrc file, and that password would be used for
> every port, every user etc.

Hmm, I would expect that a password is associated with an account
identified by some user ID.  Is there any existing usage of this
apply-to-all kind of password?

> However, the plstore backed for auth-sources currently requires that
> the keys host, user, password, and port ALL are present in the entry
> for it to successfully match.
>

I think all 4 fields are also required for other backends like netrc,
json, etc. - when Gnus trying to search for an entry through nnimap, it
tries to search using a tuple of (:host, :user, :port) and requires the
returned entry has :secret.  Or maybe I'm missing some other use case?

> I wanted some insight into this discrepancy. My goal with the
> oauth2.el changes is to have minimum viable integration with
> auth-sources such that the existing functions using it work. It's
> narrower in scope than your plugin, and perhaps when I have a final
> patchset ready we can discuss the merits of each.
>

Definitely, sounds good.

> Thanks
> -- 
> Soham Gumaste
> sohamg2@gmail.com

-- 
Regards,
Xiyue Deng

signature.asc
Description: PGP signature