Add support for pluggable Custom Presto Authenticators

[imsayari404]

Description

A pluggable authenticator in Presto allows the authentication process to be customized based on specific use cases, such as integrating with different identity providers or token validation strategies.

Motivation and Context

Fixes #24052

Test Plan

Added Unit Tests

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

Security Changes
* Add support for pluggable Custom Presto Authenticators :pr:`#24111`

[pramodsatya]

Thanks @imsayari404, could you please add a test? Will the JwtAuthenticator and PasswordAuthenticator be refactored, as suggested in #24053 (review), in this PR?

[pramodsatya]

Should this be an interface?

[imsayari404]

The PrestoAuthenticator class does not need to be an interface because it serves as a concrete adapter between the Airlift Authenticator interface and the pluggable design provided by PrestoAuthenticator and PrestoAuthenticatorFactory SPI. Its role is to delegate authentication to the PrestoAuthenticatorManager.

[imjalpreet]

@pramodsatya I understand why you might be confused. We have an interface called PrestoAuthenticator in the presto-spi package with the same name.

@tdcmeehan Currently, we've followed the same naming convention as was done for the PasswordAuthenticator SPI. This could lead to confusion since we have an SPI with the same name as the PasswordAuthenticator class in the presto-main package. Do you think we should refactor the class names in presto-main to eliminate the confusion?

[steveburnett]

Thanks for the doc! A couple of rephrasing suggestions for conciseness.

Also - because this is a new page - you must add

develop/presto-authenticator

to https://github.com/prestodb/presto/blob/master/presto-docs/src/main/sphinx/develop.rst

so the new page will show up on the Developer Guide index page https://prestodb.io/docs/current/develop.html .

[steveburnett]

Suggested change

	Presto supports authentication via a custom presto authenticator
	Presto supports authentication through a custom Presto authenticator

Don't use via. See the GitLab documentation style guide word list entry for via for discussion and alternate working suggestions, if the suggested through isn't a good fit for you.

[steveburnett]

Suggested change

	``PrestoAuthenticatorFactory`` is responsible for creating a
	``PrestoAuthenticatorFactory`` creates a

[steveburnett]

Suggested change

	Below property needs to be added to the coordinator's ``config.properties`` file:
	Add the property shown below to the coordinator's ``config.properties`` file:

[imjalpreet]

Will the JwtAuthenticator and PasswordAuthenticator be refactored, as suggested in #24053 (review), in this PR?

@pramodsatya There has been a slight change since my last comment on this issue. After discussions with @tdcmeehan, we introduced a new and more generic SPI that is independent of the current Authenticators. This SPI can be used to implement any type of custom authenticator, without being limited to just a custom implementation of JWT or Password Authenticators.

We decided to keep the current implementation of Password and JWT authenticators unchanged to avoid introducing a breaking change.