• Home
• com.ovea.tajin.framework
• tajin-framework-all
• 2.0.b6
• source code
• package-info.java

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

org.apache.shiro.authz.package-info Maven / Gradle / Ivy

/*
 * 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.
 */
/**
 * Core interfaces and exceptions supporting Authorization (access control).
 * 

 * Shiro abbreviates the word 'AuthoriZation' as authz to distinguish it seperately from
 * 'AuthentiCation', abbreviated as authc.
 * 

 * This package's primary interface of interest, which is the core of Shiro authorization functionality,
 * is the Authorizer. This interface handles all aspects of principal-related security and is the
 * facade to all other Shiro authorization components.
 * 

 * Shiro has the ability to authorize subjects (a.k.a. users) without being intrusive to the application's
 * domain model. Most applications will utilize the concepts of groups, roles, and
 * permissions, but Shiro tries to be as non-invasive as possible doesn't require any such
 * interfaces (although a Permission interface is made available for fine-grained access control policies if
 * you want to use Shiro's permission support out-of-the-box).
 * 

 * Although it is possible for applications to implement this and other interfaces directly, it is not
 * recommended. Shiro already has base implementations which should be suitable for 99% of deployments.
 */
package org.apache.shiro.authz;