[
https://issues.apache.org/jira/browse/GEODE-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262047#comment-17262047
]
ASF GitHub Bot commented on GEODE-8782:
---------------------------------------
jdeppe-pivotal commented on pull request #5880:
URL: https://github.com/apache/geode/pull/5880#issuecomment-757009606
> Historically we have never changed serialization version between patches
releases. Gfsh used to rely on this but now I think will be fine, but we still
may encounter some surprises. Also GEODE_1_12_1 (and this entire change) will
need to be added to support/1.13 and develop if hasn't been already.
Yes, that's correct, but I don't think we can actually do that yet until we
have an actual `1.12.1` release to point to. Correct me if that's not right.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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.12.1, 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)
