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 */
019 package org.apache.shiro.realm;
020
021 import org.apache.shiro.authc.AuthenticationException;
022 import org.apache.shiro.authc.AuthenticationInfo;
023 import org.apache.shiro.authc.AuthenticationToken;
024 import org.apache.shiro.authz.Authorizer;
025
026
027 /**
028 * A <tt>Realm</tt> is a security component that can access application-specific security entities
029 * such as users, roles, and permissions to determine authentication and authorization operations.
030 *
031 * <p><tt>Realm</tt>s usually have a 1-to-1 correspondance with a datasource such as a relational database,
032 * file sysetem, or other similar resource. As such, implementations of this interface use datasource-specific APIs to
033 * determine authorization data (roles, permissions, etc), such as JDBC, File IO, Hibernate or JPA, or any other
034 * Data Access API. They are essentially security-specific
035 * <a href="http://en.wikipedia.org/wiki/Data_Access_Object" target="_blank">DAO</a>s.
036 *
037 * <p>Because most of these datasources usually contain Subject (a.k.a. User) information such as usernames and
038 * passwords, a Realm can act as a pluggable authentication module in a
039 * <a href="http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules">PAM</a> configuration. This allows a Realm to
040 * perform <i>both</i> authentication and authorization duties for a single datasource, which caters to the large
041 * majority of applications. If for some reason you don't want your Realm implementation to perform authentication
042 * duties, you should override the {@link #supports(org.apache.shiro.authc.AuthenticationToken)} method to always
043 * return <tt>false</tt>.
044 *
045 * <p>Because every application is different, security data such as users and roles can be
046 * represented in any number of ways. Shiro tries to maintain a non-intrusive development philosophy whenever
047 * possible - it does not require you to implement or extend any <tt>User</tt>, <tt>Group</tt> or <tt>Role</tt>
048 * interfaces or classes.
049 *
050 * <p>Instead, Shiro allows applications to implement this interface to access environment-specific datasources
051 * and data model objects. The implementation can then be plugged in to the application's Shiro configuration.
052 * This modular technique abstracts away any environment/modeling details and allows Shiro to be deployed in
053 * practically any application environment.
054 *
055 * <p>Most users will not implement the <tt>Realm</tt> interface directly, but will extend one of the subclasses,
056 * {@link org.apache.shiro.realm.AuthenticatingRealm AuthenticatingRealm} or {@link org.apache.shiro.realm.AuthorizingRealm}, greatly reducing the effort requird
057 * to implement a <tt>Realm</tt> from scratch.</p>
058 *
059 * @author Les Hazlewood
060 * @author Jeremy Haile
061 * @see org.apache.shiro.realm.CachingRealm CachingRealm
062 * @see org.apache.shiro.realm.AuthenticatingRealm AuthenticatingRealm
063 * @see org.apache.shiro.realm.AuthorizingRealm AuthorizingRealm
064 * @see org.apache.shiro.authc.pam.ModularRealmAuthenticator ModularRealmAuthenticator
065 * @since 0.1
066 */
067 public interface Realm extends Authorizer {
068
069 /**
070 * Returns the (application-unique) name assigned to this <code>Realm</code>. All realms configured for a single
071 * application must have a unique name.
072 *
073 * @return the (application-unique) name assigned to this <code>Realm</code>.
074 */
075 String getName();
076
077 /**
078 * Returns <tt>true</tt> if this realm wishes to authenticate the Subject represented by the given
079 * {@link org.apache.shiro.authc.AuthenticationToken AuthenticationToken} instance, <tt>false</tt> otherwise.
080 *
081 * <p>If this method returns <tt>false</tt>, it will not be called to authenticate the Subject represented by
082 * the token - more specifically, a <tt>false</tt> return value means this Realm instance's
083 * {@link #getAuthenticationInfo} method will not be invoked for that token.
084 *
085 * @param token the AuthenticationToken submitted for the authentication attempt
086 * @return <tt>true</tt> if this realm can/will authenticate Subjects represented by specified token,
087 * <tt>false</tt> otherwise.
088 */
089 boolean supports(AuthenticationToken token);
090
091 /**
092 * Returns an account's authentication-specific information for the specified <tt>token</tt>,
093 * or <tt>null</tt> if no account could be found based on the <tt>token</tt>.
094 *
095 * <p>This method effectively represents a login attempt for the corresponding user with the underlying EIS datasource.
096 * Most implementations merely just need to lookup and return the account data only (as the method name implies)
097 * and let Shiro do the rest, but implementations may of course perform eis specific login operations if so
098 * desired.
099 *
100 * @param token the application-specific representation of an account principal and credentials.
101 * @return the authentication information for the account associated with the specified <tt>token</tt>,
102 * or <tt>null</tt> if no account could be found.
103 * @throws org.apache.shiro.authc.AuthenticationException
104 * if there is an error obtaining or constructing an AuthenticationInfo object based on the
105 * specified <tt>token</tt> or implementation-specifc login behavior fails.
106 */
107 AuthenticationInfo getAuthenticationInfo(AuthenticationToken token) throws AuthenticationException;
108
109 }