[
https://issues.apache.org/jira/browse/JAMES-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18110590#comment-18110590
]
Benoit Tellier commented on JAMES-4215:
---------------------------------------
The current implem works but hard code that the kerberos principal left part IS
the domain of the mail address
But in real world deployment this is not guarantied to be the case: kerberos
real might be `kb.domain.tld`
I propose to add a mapping realm -> domain to enable configuring this.
Alternative considered: SPI allowing to load custom code for pincipal ->
username mapping. This can come in a second time if truely needed.
See https://github.com/apache/james-project/pull/3146
> Add SASL GSSAPI (Kerberos V5) authentication mechanism
> ------------------------------------------------------
>
> Key: JAMES-4215
> URL: https://issues.apache.org/jira/browse/JAMES-4215
> Project: James Server
> Issue Type: New Feature
> Affects Versions: master
> Reporter: Tran Hong Quan
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> For a customer use case, we plan to extend Apache James SASL support with the
> GSSAPI mechanism, enabling Kerberos-based authentication, cf
> https://www.rfc-editor.org/info/rfc4752.
> This would integrate with James's existing SASL authentication infrastructure
> and be available to applicable protocols.
> Is this a topic that the James community would be interested in?
> We would like to confirm whether the James community is interested in
> receiving this contribution. Without community interest or feedback, we may
> instead implement and maintain it in TMail Backend.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
