GitHub user vijikarthi opened a pull request:

    https://github.com/apache/flink/pull/2425

    FLINK-3930 Added shared secret based authorization for Flink service …

    This PR addresses FLINK-3930 requirements. It enables shared secret based 
secure cookie authorization for the following components
    
    - Akka layer
    - Blob Service
    - Web UI
    
    Secure cookie authentication can be enabled by providing below 
configurations to Flink configuration file.
    
    - `security.enabled`: A boolean value (true|false) indicating security is 
enabled or not.
    - `security.cookie` : Secure cookie value to be used for authentication. 
For standalone deployment mode, the secure cookie value is mandatory when 
security is enabled but for the Yarn mode it is optional (auto-generated if not 
provided).
    
    Alternatively, secure cookie value can be provided through Flink/Yarn CLI 
using "-k" or "--cookie" parameter option.
    
    The web runtime module prompts for secure cookie using standard basic HTTP 
authentication mechanism, where the user id field is a noop and the password 
field will be used to capture the secure cookie. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vijikarthi/flink FLINK-3930

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2425.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 #2425
    
----
commit 33d391cb17e68dd203328a91fa6b63218884b49d
Author: Vijay Srinivasaraghavan <vijayaraghavan.srinivasaragha...@emc.com>
Date:   2016-08-26T19:02:20Z

    FLINK-3930 Added shared secret based authorization for Flink service 
components

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to