[
https://issues.apache.org/jira/browse/NIFI-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296975#comment-16296975
]
ASF subversion and git services commented on NIFI-4005:
-------------------------------------------------------
Commit 17ddaf6be0d4c75aa8b0d86f84f1f90757f8368f in nifi's branch
refs/heads/master from [~aperepel]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=17ddaf6 ]
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
> Assignee: Koji Kawamura
> 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.4.14#64029)
