anujmodi2021 opened a new pull request, #6552:
URL: https://github.com/apache/hadoop/pull/6552

   ### Description of PR
   Jira: https://issues.apache.org/jira/browse/HADOOP-18516
   Changes ported from PR: https://github.com/apache/hadoop/pull/5148
   
   This PR introduces a new configuration for Fixed SAS Tokens.
   
   Using this new configuration fs.azure.sas.fixed.token, 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.
   A change for appending SAS Tokens to the queries of 4 filesystem level APIs 
is also introduced, helped by the introduction of the fixed token. When an 
Account SAS Token is configured as the fixed SAS Token, and it is used, it is 
ensured that these operations are within the scope of the SAS Token. The 
configuration introduced also bypasses the need for having an implementation of 
the SASTokenProvider interface in cases where a token simply be directly set.
   
   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 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.
   
   ### How was this patch tested?
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to