https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38338

David Cook <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA

--- Comment #87 from David Cook <[email protected]> ---
I've actually created a simple SASL plugin for the XOAUTH2 mechanism in C:
https://github.com/minusdavid/simple-sasl-xoauth2

I still need to improve the documentation, and I've got a bit more polishing I
want to do, but it's a functional C equivalent of Authen::SASL::Perl::XOAUTH2,
and I've tested it in Perl using Authen::SASL::XS as well, which was good fun.

In the past, I've tested C SASL plugins using Postfix, but now I can just use
Authen::SASL::XS and Net::SMTP. I don't even have to send the email. I can just
check that the authentication succeeds and then end the connection.

Of course, that leads to the same issue we have here in Koha. While we have
SASL plugins that can perform the SASL authentication, we need a provider for
the plugins. 

--

For Postfix, my plan is to write a daemon that Postfix will call using a
socketmap lookup, so a Perl or Golang daemon will create a Unix socket, Postfix
will connect to that and send some query information, and the daemon will
return the authentication credentials (including username and OAuth2 token).

For Koha, we could build it in. Koha::SASL::Helpers or something. I've got an
idea for this one...

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to