All Downloads are FREE. Search and download functionalities are using the official Maven repository.

org.apache.shiro.authz.permission.WildcardPermission Maven / Gradle / Ivy

There is a newer version: 3.9
Show newest version
/*
 * 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.
 */
package org.apache.shiro.authz.permission;

import org.apache.shiro.authz.Permission;
import org.apache.shiro.util.CollectionUtils;

import java.io.Serializable;
import java.util.ArrayList;
import java.util.LinkedHashSet;
import java.util.List;
import java.util.Set;

/**
 * A WildcardPermission is a very flexible permission construct supporting multiple levels of
 * permission matching. However, most people will probably follow some standard conventions as explained below.
 * 

*

Simple Usage

*

* In the simplest form, WildcardPermission can be used as a simple permission string. You could grant a * user an "editNewsletter" permission and then check to see if the user has the editNewsletter * permission by calling *

* subject.isPermitted("editNewsletter") *

* This is (mostly) equivalent to *

* subject.isPermitted( new WildcardPermission("editNewsletter") ) *

* but more on that later. *

* The simple permission string may work for simple applications, but it requires you to have permissions like * "viewNewsletter", "deleteNewsletter", * "createNewsletter", etc. You can also grant a user "*" permissions * using the wildcard character (giving this class its name), which means they have all permissions. But * using this approach there's no way to just say a user has "all newsletter permissions". *

* For this reason, WildcardPermission supports multiple levels of permissioning. *

*

Multiple Levels

*

* WildcardPermission also supports the concept of multiple levels. For example, you could * restructure the previous simple example by granting a user the permission "newsletter:edit". * The colon in this example is a special character used by the WildcardPermission that delimits the * next token in the permission. *

* In this example, the first token is the domain that is being operated on * and the second token is the action being performed. Each level can contain multiple values. So you * could simply grant a user the permission "newsletter:view,edit,create" which gives them * access to perform view, edit, and create actions in the newsletter * domain. Then you could check to see if the user has the "newsletter:create" * permission by calling *

* subject.isPermitted("newsletter:create") *

* (which would return true). *

* In addition to granting multiple permissions via a single string, you can grant all permission for a particular * level. So if you wanted to grant a user all actions in the newsletter domain, you could simply give * them "newsletter:*". Now, any permission check for "newsletter:XXX" * will return true. It is also possible to use the wildcard token at the domain level (or both): so you * could grant a user the "view" action across all domains "*:view". *

*

Instance-level Access Control

*

* Another common usage of the WildcardPermission is to model instance-level Access Control Lists. * In this scenario you use three tokens - the first is the domain, the second is the action, and * the third is the instance you are acting on. *

* So for example you could grant a user "newsletter:edit:12,13,18". In this example, assume * that the third token is the system's ID of the newsletter. That would allow the user to edit newsletters * 12, 13, and 18. This is an extremely powerful way to express permissions, * since you can now say things like "newsletter:*:13" (grant a user all actions for newsletter * 13), "newsletter:view,create,edit:*" (allow the user to * view, create, or edit any newsletter), or * "newsletter:*:* (allow the user to perform any action on any newsletter). *

* To perform checks against these instance-level permissions, the application should include the instance ID in the * permission check like so: *

* subject.isPermitted( "newsletter:edit:13" ) *

* There is no limit to the number of tokens that can be used, so it is up to your imagination in terms of ways that * this could be used in your application. However, the Shiro team likes to standardize some common usages shown * above to help people get started and provide consistency in the Shiro community. * * @since 0.9 */ public class WildcardPermission implements Permission, Serializable { //TODO - JavaDoc methods /*-------------------------------------------- | C O N S T A N T S | ============================================*/ protected static final String WILDCARD_TOKEN = "*"; protected static final String PART_DIVIDER_TOKEN = ":"; protected static final String SUBPART_DIVIDER_TOKEN = ","; protected static final boolean DEFAULT_CASE_SENSITIVE = false; /*-------------------------------------------- | I N S T A N C E V A R I A B L E S | ============================================*/ private List> parts; /*-------------------------------------------- | C O N S T R U C T O R S | ============================================*/ /** * Default no-arg constructor for subclasses only - end-user developers instantiating Permission instances must * provide a wildcard string at a minimum, since Permission instances are immutable once instantiated. *

* Note that the WildcardPermission class is very robust and typically subclasses are not necessary unless you * wish to create type-safe Permission objects that would be used in your application, such as perhaps a * {@code UserPermission}, {@code SystemPermission}, {@code PrinterPermission}, etc. If you want such type-safe * permission usage, consider subclassing the {@link DomainPermission DomainPermission} class for your needs. */ protected WildcardPermission() { } public WildcardPermission(String wildcardString) { this(wildcardString, DEFAULT_CASE_SENSITIVE); } public WildcardPermission(String wildcardString, boolean caseSensitive) { setParts(wildcardString, caseSensitive); } protected void setParts(String wildcardString) { setParts(wildcardString, DEFAULT_CASE_SENSITIVE); } protected void setParts(String wildcardString, boolean caseSensitive) { if (wildcardString == null || wildcardString.trim().length() == 0) { throw new IllegalArgumentException("Wildcard string cannot be null or empty. Make sure permission strings are properly formatted."); } wildcardString = wildcardString.trim(); List parts = CollectionUtils.asList(wildcardString.split(PART_DIVIDER_TOKEN)); this.parts = new ArrayList>(); for (String part : parts) { Set subparts = CollectionUtils.asSet(part.split(SUBPART_DIVIDER_TOKEN)); if (!caseSensitive) { subparts = lowercase(subparts); } if (subparts.isEmpty()) { throw new IllegalArgumentException("Wildcard string cannot contain parts with only dividers. Make sure permission strings are properly formatted."); } this.parts.add(subparts); } if (this.parts.isEmpty()) { throw new IllegalArgumentException("Wildcard string cannot contain only dividers. Make sure permission strings are properly formatted."); } } private Set lowercase(Set subparts) { Set lowerCasedSubparts = new LinkedHashSet(subparts.size()); for (String subpart : subparts) { lowerCasedSubparts.add(subpart.toLowerCase()); } return lowerCasedSubparts; } /*-------------------------------------------- | A C C E S S O R S / M O D I F I E R S | ============================================*/ protected List> getParts() { return this.parts; } /*-------------------------------------------- | M E T H O D S | ============================================*/ public boolean implies(Permission p) { // By default only supports comparisons with other WildcardPermissions if (!(p instanceof WildcardPermission)) { return false; } WildcardPermission wp = (WildcardPermission) p; List> otherParts = wp.getParts(); int i = 0; for (Set otherPart : otherParts) { // If this permission has less parts than the other permission, everything after the number of parts contained // in this permission is automatically implied, so return true if (getParts().size() - 1 < i) { return true; } else { Set part = getParts().get(i); if (!part.contains(WILDCARD_TOKEN) && !part.containsAll(otherPart)) { return false; } i++; } } // If this permission has more parts than the other parts, only imply it if all of the other parts are wildcards for (; i < getParts().size(); i++) { Set part = getParts().get(i); if (!part.contains(WILDCARD_TOKEN)) { return false; } } return true; } public String toString() { StringBuilder buffer = new StringBuilder(); for (Set part : parts) { if (buffer.length() > 0) { buffer.append(":"); } buffer.append(part); } return buffer.toString(); } public boolean equals(Object o) { if (o instanceof WildcardPermission) { WildcardPermission wp = (WildcardPermission) o; return parts.equals(wp.parts); } return false; } public int hashCode() { return parts.hashCode(); } }





© 2015 - 2025 Weber Informatics LLC | Privacy Policy