You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/04/19 21:21:00 UTC
[jira] [Commented] (GEODE-2652) IntegratedSecurityService class has
state that is not thread safe
[ https://issues.apache.org/jira/browse/GEODE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444821#comment-16444821 ]
Anthony Baker commented on GEODE-2652:
--------------------------------------
[~khowe] is this still an issue?
> IntegratedSecurityService class has state that is not thread safe
> -----------------------------------------------------------------
>
> Key: GEODE-2652
> URL: https://issues.apache.org/jira/browse/GEODE-2652
> Project: Geode
> Issue Type: Bug
> Components: security
> Reporter: Kirk Lund
> Priority: Major
>
> The state of IntegratedSecurityService is currently not thread safe. One thread may set these values by invoking initSecurity, while others threads invoke methods which access these values:
> * private PostProcessor postProcessor;
> * private SecurityManager securityManager;
> * private Boolean isIntegratedSecurity;
> * private boolean isClientAuthenticator; // is there a SECURITY_CLIENT_AUTHENTICATOR
> * private boolean isPeerAuthenticator; // is there a SECURITY_PEER_AUTHENTICATOR
> This could manifest as thread visibility bugs (other thread does not see the value set by another thread).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)