---
title:  Managing a Cache in a Secure System
---

<!--
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.
-->

A secured system does both authentication at connection time
and authorization prior to cache operations.
Client apps and cluster members (servers and locators) require
configuration and setup when the `SecurityManager` is enabled.

See the section on  [Security](../../security/chapter_overview.html)
for details.
For authentication, see 
[Implementing Authentication](../../security/implementing_authentication.html).
