[
https://issues.apache.org/jira/browse/NIFI-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035328#comment-16035328
]
ASF GitHub Bot commented on NIFI-4005:
--------------------------------------
GitHub user aperepel opened a pull request:
https://github.com/apache/nifi/pull/1886
NIFI-4005 Add support for Azure Shared Access Signature (SAS) Tokens
- Refactoring and cleanup
- Upgraded the client library from 5.0.0 to 5.2.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aperepel/nifi NIFI-4005
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1886.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1886
----
commit 0ae8b2ffdf169724850a583668d3702af5516345
Author: Andrew Grande <[email protected]>
Date: 2017-05-31T20:45:26Z
NIFI-4005 Add support for Azure Shared Access Signature (SAS) Tokens.
Upgraded the client library from 5.0.0 to 5.2.0
----
> Add support for Azure Shared Access Signature (SAS) Tokens
> ----------------------------------------------------------
>
> Key: NIFI-4005
> URL: https://issues.apache.org/jira/browse/NIFI-4005
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.2.0
> Reporter: Andrew Grande
> Priority: Minor
>
> Azure's account name and key are treated as admin, 'root' access credentials.
> If one has those, every container under this account is fully accessible. An
> MSFT-recommended approach is to use SAS policies, which provide for a fine
> grained permission and object control, as well as defined expiration.
> I already have working code, filing this ticket to formally track and submit
> PR against next.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
