From e9543b49c4a4d959e32315a208c7e3d9f099926d Mon Sep 17 00:00:00 2001 From: alexcom Date: Thu, 12 Jan 2017 14:45:53 +0200 Subject: [PATCH] typo in Kerberos word Fixes: #5 --- authorization-features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/authorization-features.md b/authorization-features.md index ef2f44ade9..f30694abd2 100644 --- a/authorization-features.md +++ b/authorization-features.md @@ -18,7 +18,7 @@ Authorization is a critical element of any application but it can quickly become * **Strong caching support** - Any of the modern open-source and/or enterprise caching products can be plugged in to Shiro to provide a fast and efficient user-experience. For authorization, caching is crucial for performance in larger environments or with more complex policies using back-end security data sources. -* **Pluggable data sources** - Shiro uses pluggable data access objects, referred to as Realms, to connect to security data sources where you keep your access control information, like a LDAP or a relational database. To help you avoid building and maintaining integrations yourself, Shiro provides out-of-the-box realms for popular data sources like LDAP, Active Directory, Kerboros, and JDBC. If needed, you can also create your own realms to support specific functionality not included in the basic realms. +* **Pluggable data sources** - Shiro uses pluggable data access objects, referred to as Realms, to connect to security data sources where you keep your access control information, like a LDAP or a relational database. To help you avoid building and maintaining integrations yourself, Shiro provides out-of-the-box realms for popular data sources like LDAP, Active Directory, Kerberos, and JDBC. If needed, you can also create your own realms to support specific functionality not included in the basic realms. * **Supports any data model** - Shiro can support any data model for access control-- it doesn't force a model on you. Your realm implementation ultimately decides how your permissions and roles are grouped together and whether to return a "yes" or a "no" answer to Shiro. This feature allows you to architect your application in the manner you chose and Shiro will bend to support you.