Re: Interest in SASL GSSAPI / Kerberos support?

Quan tran hong <[email protected]> Thu, 16 Jul 2026 14:43:06 +0700
Newsgroups gmane.comp.jakarta.james.devel
Message-ID <CAFG0j1C4cQNSXsQs09drD9jJqmjvzhFq9rwHeP2LzuVH2N3eTQ@mail.gmail.com>
--000000000000eb707e0656b5973c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Benoit,

Thanks for your suggestion. I will try to propose a prototype
regarding this topic next week.

Regards,

Quan

On Thu, Jul 16, 2026 at 2:37=E2=80=AFPM Benoit TELLIER <[email protected]=
om>
wrote:

> Hello Quan,
>
> Following the rule of thunb "it's a standard with a RFC" I think it makes
> sense to lend this in James codebase.
>
> My personal preference would be as a guice extension jars, in
> `protocols/sasl-kerberos`
> --
>
>
> Best regards,
>
> Benoit TELLIER
>
> General manager of Linagora VIETNAM.
> Product owner for Twake-Mail product.
> Chairman of the Apache James project.
>
> Mail: [email protected]
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>
>
>
> On Jul 16, 2026 9:23 AM, from Quan Tran Hong <[email protected]=
>Hi
> James community,
>
> For a customer use case, we are considering extending Apache James SASL
> support with the GSSAPI mechanism, enabling Kerberos-based authentication
> as specified by RFC 4752 <rfc-editor.org/rfc/rfc4752.html>.
>
> Related Jira ticket: issues.apache.org/jira/browse/JAMES-4215.
>
> The intention would be to integrate it with James=E2=80=99s existing SASL
> infrastructure and make it available to applicable protocols.
>
> Would the community be interested in receiving and maintaining this
> contribution upstream? If not, we may instead implement and maintain it i=
n
> TMail Backend.
>
> Regards,
> Quan
>

--000000000000eb707e0656b5973c--