[
https://issues.apache.org/jira/browse/GEODE-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261603#comment-17261603
]
ASF subversion and git services commented on GEODE-8782:
--------------------------------------------------------
Commit 0ab677199d189527be354fd1427ce29b91ed6b31 in geode's branch
refs/heads/support/1.12 from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0ab6771 ]
GEODE-8782: Add getPrincipal method to FunctionContext interface (#5840) (#5880)
- Add the ability to retrieve the Principal from the FunctionContext
when a SecurityManager is enabled.
(cherry picked from commit a42f89ab48aaca9aac96a34e80a9b3b2d46bcddd)
> Add getPrincipal method to FunctionContext interface
> ----------------------------------------------------
>
> Key: GEODE-8782
> URL: https://issues.apache.org/jira/browse/GEODE-8782
> Project: Geode
> Issue Type: New Feature
> Components: core
> Reporter: Jens Deppe
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> In some cases it would be very helpful to have access to the {{Principal}}
> when executing a function.
> It may seem obvious that if one has a reference to the {{cache}} that you
> could get to the {{SecurityManager}} and extract the {{Subject}} and thus the
> {{Principal}} from there. However, in some cases, Geode will seamlessly proxy
> a function call from one server to the other. This will typically happen with
> {{onRegion}} calls and partitioned regions. In such cases, the security
> context is lost and thus the principal is not accessible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
