geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-3447) Implement client authorization for the new protocol
Date Fri, 25 Aug 2017 20:50:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142167#comment-16142167
] 

ASF GitHub Bot commented on GEODE-3447:
---------------------------------------

Github user galen-pivotal commented on the issue:

    https://github.com/apache/geode/pull/719
  
    @metatype We need the `StreamAuthenticator` to receive and send (Protobuf-encoded) messages
containing the credentials that get passed to the `SecurityManager`. I would think that ideally
it's nothing more than this.
    
    I wonder if it would be better to send a hash that gets put into the Properties that SecurityManager
uses, rather than having a message that explicitly contains username and password.


> Implement client authorization for the new protocol
> ---------------------------------------------------
>
>                 Key: GEODE-3447
>                 URL: https://issues.apache.org/jira/browse/GEODE-3447
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server
>            Reporter: Brian Baynes
>            Assignee: Bruce Schuchardt
>
> As a user of the new client/server protocol, I need to make sure the clients using the
protocol to access my grid are authorized to perform each operation they attempt.
> Implement client authorization for operations in new protocol based on existing authorization
configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message