| --- |
| title: Post-Operative Authorization |
| --- |
| |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| |
| Authorization in the post-operation phase occurs on the server after the operation is complete and before the results are sent to the client. |
| |
| The callback can modify the results of certain operations, such as `query`, `get` and `keySet`, or even completely disallow the operation. For example, a post-operation callback for a query operation can filter out sensitive data or data that the client should not receive, or even completely fail the operation. |
| |
| The `security-client-accessor-pp` system property in the server’s `gemfire.properties` file specifies the callback to invoke in the post-operation phase. For example: |
| |
| ``` pre |
| security-client-accessor-pp=templates.security.XmlAuthorization.create |
| ``` |
| |
| |
