This is an automated email from the ASF dual-hosted git repository.
fpapon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shiro-site.git
The following commit(s) were added to refs/heads/master by this push:
new 166acb9 Update realm.md.vtl
new 8acbbcd Merge pull request #65 from Amitsharma0201/master
166acb9 is described below
commit 166acb91287388c15516aaba4f2dc0fc80bf67bc
Author: Amitsharma0201 <[email protected]>
AuthorDate: Thu Oct 1 17:20:23 2020 +0530
Update realm.md.vtl
---
realm.md.vtl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/realm.md.vtl b/realm.md.vtl
index f22729c..a8d57e6 100644
--- a/realm.md.vtl
+++ b/realm.md.vtl
@@ -24,7 +24,7 @@
* [Role based Authorization](#Realm-RoleBasedAuthorization)
* [Permission based Authorization](#Realm-PermissionBasedAuthorization)
-A `Realm` is a component that can access application-specific security data
such as users, roles, and permissions. The `Realm` translates this
application-specific data into a format that Shiro understands so Shiro can in
turn provide a single easy-to-understand [Subject](subject.html "Subject")
programming API no matter how many data sources exist or how
application-specific your data might be.
+A `Realm` is a component that can access application-specific security data
such as users, roles and permissions. The `Realm` translates this
application-specific data into a format that Shiro understands so Shiro can in
turn provide a single easy-to-understand [Subject](subject.html "Subject")
programming API no matter how many data sources exist or how
application-specific your data might be.
Realms usually have a 1-to-1 correlation with a data source such as a
relational database, LDAP directory, file system, or other similar resource. As
such, implementations of the `Realm` interface use data source-specific APIs to
discover authorization data (roles, permissions, etc), such as JDBC, File IO,
Hibernate or JPA, or any other Data Access API.
