001/* 002 Licensed to the Apache Software Foundation (ASF) under one 003 or more contributor license agreements. See the NOTICE file 004 distributed with this work for additional information 005 regarding copyright ownership. The ASF licenses this file 006 to you under the Apache License, Version 2.0 (the 007 "License"); you may not use this file except in compliance 008 with the License. You may obtain a copy of the License at 009 010 http://www.apache.org/licenses/LICENSE-2.0 011 012 Unless required by applicable law or agreed to in writing, 013 software distributed under the License is distributed on an 014 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 015 KIND, either express or implied. See the License for the 016 specific language governing permissions and limitations 017 under the License. 018 */ 019package org.apache.wiki.auth; 020 021import org.apache.wiki.api.core.Context; 022import org.apache.wiki.api.core.Session; 023import org.apache.wiki.api.engine.Initializable; 024import org.apache.wiki.auth.authorize.Role; 025import org.apache.wiki.event.WikiEventListener; 026import org.apache.wiki.event.WikiEventManager; 027 028import jakarta.servlet.http.HttpServletResponse; 029import java.io.IOException; 030import java.security.AccessController; 031import java.security.Permission; 032import java.security.Principal; 033import org.apache.wiki.event.WikiSecurityEvent; 034import org.apache.wiki.security.EventUtil; 035 036 037/** 038 * <p>Manages all access control and authorization; determines what authenticated users are allowed to do.</p> 039 * <p>Privileges in JSPWiki are expressed as Java-standard {@link java.security.Permission} classes. There are two types of permissions:</p> 040 * <ul> 041 * <li>{@link org.apache.wiki.auth.permissions.WikiPermission} - privileges that apply to an entire wiki instance: <em>e.g.,</em> 042 * editing user profiles, creating pages, creating groups</li> 043 * <li>{@link org.apache.wiki.auth.permissions.PagePermission} - privileges that apply to a single wiki page or range of pages: 044 * <em>e.g.,</em> reading, editing, renaming 045 * </ul> 046 * <p>Calling classes determine whether they are entitled to perform a particular action by constructing the appropriate permission first, 047 * then passing it and the current {@link Session} to the {@link #checkPermission(Session, Permission)} method. If 048 * the session's Subject possesses the permission, the action is allowed.</p> 049 * <p>For WikiPermissions, the decision criteria is relatively simple: the caller either possesses the permission, as granted by the wiki 050 * security policy -- or not.</p> 051 * <p>For PagePermissions, the logic is exactly the same if the page being checked does not have an access control list. However, if the 052 * page does have an ACL, the authorization decision is made based the <em>union</em> of the permissions granted in the ACL and in the 053 * security policy. In other words, the user must be named in the ACL (or belong to a group or role that is named in the ACL) <em>and</em> 054 * be granted (at least) the same permission in the security policy. We do this to prevent a user from gaining more permissions than they 055 * already have, based on the security policy.</p> 056 * <p>See the implementation on {@link #checkPermission(Session, Permission)} method for more information on the authorization logic.</p> 057 * 058 * @since 2.3 059 * @see AuthenticationManager 060 */ 061public interface AuthorizationManager extends Initializable { 062 063 /** The default external Authorizer is the {@link org.apache.wiki.auth.authorize.WebContainerAuthorizer} */ 064 String DEFAULT_AUTHORIZER = "org.apache.wiki.auth.authorize.WebContainerAuthorizer"; 065 066 /** Property that supplies the security policy file name, in WEB-INF. */ 067 String POLICY = "jspwiki.policy.file"; 068 069 /** Name of the default security policy file, in WEB-INF. */ 070 String DEFAULT_POLICY = "jspwiki.policy"; 071 072 /** The property name in jspwiki.properties for specifying the external {@link Authorizer}. */ 073 String PROP_AUTHORIZER = "jspwiki.authorizer"; 074 075 /** 076 * Returns <code>true</code> or <code>false</code>, depending on whether a Permission is allowed for the Subject associated with 077 * a supplied Session. The access control algorithm works this way: 078 * <ol> 079 * <li>The {@link org.apache.wiki.api.core.Acl} for the page is obtained</li> 080 * <li>The Subject associated with the current {@link org.apache.wiki.api.core.Session} is obtained</li> 081 * <li>If the Subject's Principal set includes the Role Principal that is the administrator group, always allow the Permission</li> 082 * <li>For all permissions, check to see if the Permission is allowed according to the default security policy. If it isn't, deny 083 * the permission and halt further processing.</li> 084 * <li>If there is an Acl, get the list of Principals assigned this Permission in the Acl: these will be role, group or user Principals, 085 * or {@link org.apache.wiki.auth.acl.UnresolvedPrincipal}s (see below). Then iterate through the Subject's Principal set and determine 086 * whether the user (Subject) possesses any one of these specified Roles or Principals.</li> 087 * </ol> 088 * <p> 089 * Note that when iterating through the Acl's list of authorized Principals, it is possible that one or more of the Acl's Principal 090 * entries are of type <code>UnresolvedPrincipal</code>. This means that the last time the ACL was read, the Principal (user, built-in 091 * Role, authorizer Role, or wiki Group) could not be resolved: the Role was not valid, the user wasn't found in the UserDatabase, or 092 * the Group wasn't known to (e.g., cached) in the GroupManager. If an <code>UnresolvedPrincipal</code> is encountered, this method 093 * will attempt to resolve it first <em>before</em> checking to see if the Subject possesses this principal, by calling 094 * {@link #resolvePrincipal(String)}. If the (re-)resolution does not succeed, the access check for the principal will fail by 095 * definition (the Subject should never contain UnresolvedPrincipals). 096 * </p> 097 * <p> 098 * If security not set to JAAS, will return true. 099 * </p> 100 * 101 * @param session the current wiki session 102 * @param permission the Permission being checked 103 * @return the result of the Permission check 104 */ 105 boolean checkPermission( Session session, Permission permission ); 106 107 /** 108 * <p>Determines if the Subject associated with a supplied Session contains a desired Role or GroupPrincipal. The algorithm 109 * simply checks to see if the Subject possesses the Role or GroupPrincipal it in its Principal set. Note that any user (anonymous, 110 * asserted, authenticated) can possess a built-in role. But a user <em>must</em> be authenticated to possess a role other than one 111 * of the built-in ones. We do this to prevent privilege escalation.</p> 112 * <p>For all other cases, this method returns <code>false</code>.</p> 113 * <p>Note that this method does <em>not</em> consult the external Authorizer or GroupManager; it relies on the Principals that 114 * have been injected into the user's Subject at login time, or after group creation/modification/deletion.</p> 115 * 116 * @param session the current wiki session, which must be non-null. If null, the result of this method always returns <code>false</code> 117 * @param principal the Principal (role or group principal) to look for, which must be non-<code>null</code>. If <code>null</code>, 118 * the result of this method always returns <code>false</code> 119 * @return <code>true</code> if the Subject supplied with the WikiContext posesses the Role or GroupPrincipal, <code>false</code> otherwise 120 */ 121 default boolean isUserInRole( final Session session, final Principal principal ) { 122 if ( session == null || principal == null || AuthenticationManager.isUserPrincipal( principal ) ) { 123 return false; 124 } 125 126 // Any type of user can possess a built-in role 127 if ( principal instanceof Role && Role.isBuiltInRole( (Role)principal ) ) { 128 return session.hasPrincipal( principal ); 129 } 130 131 // Only authenticated users can possess groups or custom roles 132 if ( session.isAuthenticated() && AuthenticationManager.isRolePrincipal( principal ) ) { 133 return session.hasPrincipal( principal ); 134 } 135 return false; 136 } 137 138 /** 139 * Returns the current external {@link Authorizer} in use. This method is guaranteed to return a properly-initialized Authorizer, unless 140 * it could not be initialized. In that case, this method throws a {@link org.apache.wiki.auth.WikiSecurityException}. 141 * 142 * @throws org.apache.wiki.auth.WikiSecurityException if the Authorizer could not be initialized 143 * @return the current Authorizer 144 */ 145 Authorizer getAuthorizer() throws WikiSecurityException; 146 147 /** 148 * <p>Determines if the Subject associated with a supplied Session contains a desired user Principal or built-in Role principal, 149 * OR is a member a Group or external Role. The rules are as follows:</p> 150 * <ol> 151 * <li>First, if desired Principal is a Role or GroupPrincipal, delegate to {@link #isUserInRole(Session, Principal)} and 152 * return the result.</li> 153 * <li>Otherwise, we're looking for a user Principal, so iterate through the Principal set and see if any share the same name as the 154 * one we are looking for.</li> 155 * </ol> 156 * <p><em>Note: if the Principal parameter is a user principal, the session must be authenticated in order for the user to "possess it". 157 * Anonymous or asserted sessions will never posseess a named user principal.</em></p> 158 * 159 * @param session the current wiki session, which must be non-null. If null, the result of this method always returns <code>false</code> 160 * @param principal the Principal (role, group, or user principal) to look for, which must be non-null. If null, the result of this 161 * method always returns <code>false</code> 162 * @return <code>true</code> if the Subject supplied with the WikiContext posesses the Role, GroupPrincipal or desired 163 * user Principal, <code>false</code> otherwise 164 */ 165 boolean hasRoleOrPrincipal( Session session, Principal principal ); 166 167 /** 168 * Checks whether the current user has access to the wiki context, by obtaining the required Permission ({@link Context#requiredPermission()}) 169 * and delegating the access check to {@link #checkPermission(Session, Permission)}. If the user is allowed, this method returns 170 * <code>true</code>; <code>false</code> otherwise. If access is allowed, the wiki context will be added to the request as an attribute 171 * with the key name {@link org.apache.wiki.api.core.Context#ATTR_CONTEXT}. Note that this method will automatically redirect the user to 172 * a login or error page, as appropriate, if access fails. This is NOT guaranteed to be default behavior in the future. 173 * 174 * @param context wiki context to check if it is accesible 175 * @param response the http response 176 * @return the result of the access check 177 * @throws IOException In case something goes wrong 178 */ 179 default boolean hasAccess( final Context context, final HttpServletResponse response ) throws IOException { 180 return hasAccess( context, response, true ); 181 } 182 183 /** 184 * Checks whether the current user has access to the wiki context (and 185 * optionally redirects if not), by obtaining the required Permission ({@link Context#requiredPermission()}) 186 * and delegating the access check to {@link #checkPermission(Session, Permission)}. 187 * If the user is allowed, this method returns <code>true</code>; 188 * <code>false</code> otherwise. Also, the wiki context will be added to the request as attribute 189 * with the key name {@link org.apache.wiki.api.core.Context#ATTR_CONTEXT}. 190 * 191 * @param context wiki context to check if it is accesible 192 * @param response The servlet response object 193 * @param redirect If true, makes an automatic redirect to the response 194 * @return the result of the access check 195 * @throws IOException If something goes wrong 196 */ 197 boolean hasAccess( final Context context, final HttpServletResponse response, final boolean redirect ) throws IOException; 198 199 /** 200 * Checks to see if the local security policy allows a particular static Permission. 201 * Do not use this method for normal permission checks; use {@link #checkPermission(Session, Permission)} instead. 202 * 203 * @param principals the Principals to check 204 * @param permission the Permission 205 * @return the result 206 */ 207 boolean allowedByLocalPolicy( Principal[] principals, Permission permission ); 208 209 /** 210 * Determines whether a Subject possesses a given "static" Permission as defined in the security policy file. This method uses standard 211 * Java 2 security calls to do its work. Note that the current access control context's <code>codeBase</code> is effectively <em>this 212 * class</em>, not that of the caller. Therefore, this method will work best when what matters in the policy is <em>who</em> makes the 213 * permission check, not what the caller's code source is. Internally, this method works by executing <code>Subject.doAsPrivileged</code> 214 * with a privileged action that simply calls {@link AccessController#checkPermission(Permission)}. 215 * 216 * @see AccessController#checkPermission(Permission) . A caught exception (or lack thereof) determines whether the 217 * privilege is absent (or present). 218 * @param session the Session whose permission status is being queried 219 * @param permission the Permission the Subject must possess 220 * @return <code>true</code> if the Subject possesses the permission, <code>false</code> otherwise 221 */ 222 boolean checkStaticPermission( Session session, Permission permission ); 223 224 /** 225 * <p>Given a supplied string representing a Principal's name from an Acl, this method resolves the correct type of Principal (role, 226 * group, or user). This method is guaranteed to always return a Principal. The algorithm is straightforward:</p> 227 * <ol> 228 * <li>If the name matches one of the built-in {@link org.apache.wiki.auth.authorize.Role} names, return that built-in Role</li> 229 * <li>If the name matches one supplied by the current {@link org.apache.wiki.auth.Authorizer}, return that Role</li> 230 * <li>If the name matches a group managed by the current {@link org.apache.wiki.auth.authorize.GroupManager}, return that Group</li> 231 * <li>Otherwise, assume that the name represents a user principal. Using the current {@link org.apache.wiki.auth.user.UserDatabase}, 232 * find the first user who matches the supplied name by calling {@link org.apache.wiki.auth.user.UserDatabase#find(String)}.</li> 233 * <li>Finally, if a user cannot be found, manufacture and return a generic {@link org.apache.wiki.auth.acl.UnresolvedPrincipal}</li> 234 * </ol> 235 * 236 * @param name the name of the Principal to resolve. Note: as of v3.0.0, the 237 * underlying behavior has changed. Principals can be resolved via login names only. 238 * @return the fully-resolved Principal 239 */ 240 Principal resolvePrincipal( final String name ); 241 242 243 // events processing ....................................................... 244 245 /** 246 * Registers a WikiEventListener with this instance. 247 * 248 * @param listener the event listener 249 */ 250 void addWikiEventListener( WikiEventListener listener ); 251 252 /** 253 * Un-registers a WikiEventListener with this instance. 254 * 255 * @param listener the event listener 256 */ 257 void removeWikiEventListener( final WikiEventListener listener ); 258 259 /** 260 * Fires a WikiSecurityEvent of the provided type, user, and permission to all registered listeners. 261 * 262 * @see org.apache.wiki.event.WikiSecurityEvent 263 * @param type the event type to be fired 264 * @param user the user associated with the event 265 * @param permission the permission the subject must possess 266 */ 267 default void fireEvent( final int type, final Principal user, final Object permission ) { 268 if( WikiEventManager.isListening( this ) ) { 269 WikiEventManager.fireEvent( this, 270 EventUtil.applyFrom(new WikiSecurityEvent( this, type, user, permission ) ) ); 271 } 272 } 273 274}