[
https://issues.apache.org/jira/browse/HADOOP-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anuj Modi updated HADOOP-18516:
-------------------------------
Description:
This PR introduces a new configuration for Fixed SAS Tokens:
*"fs.azure.sas.fixed.token"*
Using this new configuration, users can configure a fixed SAS Token in the
account settings files itself. Ideally, this should be used with SAS Tokens
that are scoped at a container or account level (Service or Account SAS), which
can be considered to be a constant for one account or container, over multiple
operations.
The other method of using a SAS Token remains valid as well, where a user
provides a custom implementation of the SASTokenProvider interface, using which
a SAS Token are obtained.
When an Account SAS Token is configured as the fixed SAS Token, and it is used,
it is ensured that operations are within the scope of the SAS Token.
The code checks for whether the fixed token and the token provider class
implementation are configured. In the case of both being set, preference is
given to the custom SASTokenProvider implementation. It must be noted that if
such an implementation provides a SAS Token which has a lower scope than
Account SAS, some filesystem and service level operations might be out of scope
and may not succeed.
was:Introduce a new configuration for setting the fixed account/service SAS
token in ABFS driver. This will be in addition to the implementations of the
SASTokenProvider interface that can be used for obtaining a SAS Token from the
user.
> [ABFS]: Support fixed SAS token config in addition to SAS Token Provider class
> ------------------------------------------------------------------------------
>
> Key: HADOOP-18516
> URL: https://issues.apache.org/jira/browse/HADOOP-18516
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/azure
> Affects Versions: 3.3.4
> Reporter: Sree Bhattacharyya
> Assignee: Anuj Modi
> Priority: Minor
> Labels: pull-request-available
>
> This PR introduces a new configuration for Fixed SAS Tokens:
> *"fs.azure.sas.fixed.token"*
> Using this new configuration, users can configure a fixed SAS Token in the
> account settings files itself. Ideally, this should be used with SAS Tokens
> that are scoped at a container or account level (Service or Account SAS),
> which can be considered to be a constant for one account or container, over
> multiple operations.
> The other method of using a SAS Token remains valid as well, where a user
> provides a custom implementation of the SASTokenProvider interface, using
> which a SAS Token are obtained.
> When an Account SAS Token is configured as the fixed SAS Token, and it is
> used, it is ensured that operations are within the scope of the SAS Token.
> The code checks for whether the fixed token and the token provider class
> implementation are configured. In the case of both being set, preference is
> given to the custom SASTokenProvider implementation. It must be noted that if
> such an implementation provides a SAS Token which has a lower scope than
> Account SAS, some filesystem and service level operations might be out of
> scope and may not succeed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
