[FEATURE] We have a requirement to add second authentication method in Kyuubi along with LDAP method

[mvjag]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

Describe the feature

Hi,
We have a requirement to add a custom authentication method along with LDAP authentication in Kyuubi 1.8.0. This is required for us as we would like to authenticate User to get access to Kyuubi/Spark and then would like to provide role based access to Hadoop/Ceph storage using tokens.

Motivation

As we are looking for this solution in our system, I think some other users also may need it due to their specific requirement.

Describe the solution

If we can enable the second authentication method in the configuration files that would greatly help. If we dn't use the second authentication method either we should be able to set it as 'None' or empty.

Additional context

No response

Are you willing to submit PR?

• Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
• No. I cannot submit a PR at this time.

[github-actions]

Hello @mvjag,
Thanks for finding the time to report the issue!
We really appreciate the community's efforts to improve Apache Kyuubi.

[pan3793]

Such a goal could be easily implemented via a custom authN method. But I don't oppose adding such a built-in functionality, looking forward to your PR.

[mvjag]

Thanks for responding quickly. Here the requirement is to have both LDAP and custom authentication working. Do you say we need to merge both methods in a custom authenticator?

…

On Thu, Apr 18, 2024 at 3:20 PM Cheng Pan ***@***.***> wrote: Such a goal could be easily implemented via a custom authN method. But I don't oppose adding such a built-in functionality, looking forward to your PR. — Reply to this email directly, view it on GitHub <#6317 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHBMCB52RVUCUOSESLK7LTDY56JO7AVCNFSM6AAAAABGM5GGIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRTGQ3TGOBZHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>