
io.vertx.ext.auth.authorization.impl.WildcardExpression 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. */ package io.vertx.ext.auth.authorization.impl; import java.util.*; /** * The following code has been adapted from the class WildcardPermission from * Apache Shiro *
also supports the concept of multiple * levels. For example, you could restructure the previous simple * example by granting a user the permission ** 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"newsletter:edit"
. The colon in this example is a * special character used by theWildcardPermission
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 performview
,edit
, and *create
actions in thenewsletter
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 thenewsletter
domain, you could simply give them *"newsletter:*"
. Now, any permission check for *"newsletter:XXX"
will returntrue
. 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 theWildcardPermission
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 newsletters12
,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 newsletter13
), *"newsletter:view,create,edit:*"
(allow the user to *view
,create
, oredit
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. */ class WildcardExpression { protected static final String PART_DIVIDER_TOKEN = ":"; protected static final String SUBPART_DIVIDER_TOKEN = ","; protected static final String WILDCARD_TOKEN = "*"; /*-------------------------------------------- | I N S T A N C E V A R I A B L E S | ============================================*/ private List> parts; private final String value; /*-------------------------------------------- | C O N S T R U C T O R S | ============================================*/ public WildcardExpression(String value) { Objects.requireNonNull(value); this.value = value.trim(); if (value.isEmpty()) { throw new IllegalArgumentException("Wildcard value cannot be empty"); } setParts(value); } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (!(obj instanceof WildcardExpression)) return false; WildcardExpression other = (WildcardExpression) obj; return Objects.equals(parts, other.parts); } /*-------------------------------------------- | A C C E S S O R S / M O D I F I E R S | ============================================*/ @Override public int hashCode() { return Objects.hash(parts); } /*-------------------------------------------- | M E T H O D S | ============================================*/ public boolean implies(String p) { if (p == null) { return false; } // fast path by simply testing string equality if (value.equals(p)) { return true; } // slightly slower path where we've got to convert 'p' to a wildcard return implies(new WildcardExpression(p)); } public boolean implies(WildcardExpression p) { if (p == null) { return false; } // By default only supports comparisons with other WildcardPermissions List > otherParts = p.parts; 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 (parts.size() - 1 < i) { return true; } else { Set part = parts.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 < parts.size(); i++) { Set part = parts.get(i); if (!part.contains(WILDCARD_TOKEN)) { return false; } } return true; } protected void setParts(String wildcardString) { wildcardString = wildcardString.trim(); if (wildcardString.isEmpty()) { throw new IllegalArgumentException("Wildcard string cannot be empty"); } this.parts = new ArrayList<>(); for (String part : wildcardString.split(PART_DIVIDER_TOKEN)) { Set subparts = new LinkedHashSet<>(Arrays.asList(part.split(SUBPART_DIVIDER_TOKEN))); 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."); } } public String toString() { return value; } }
© 2015 - 2025 Weber Informatics LLC | Privacy Policy