ISIS-1287: more bad links in the security docs.
Project: http://git-wip-us.apache.org/repos/asf/isis/repo Commit: http://git-wip-us.apache.org/repos/asf/isis/commit/3887fb2e Tree: http://git-wip-us.apache.org/repos/asf/isis/tree/3887fb2e Diff: http://git-wip-us.apache.org/repos/asf/isis/diff/3887fb2e Branch: refs/heads/ISIS-993 Commit: 3887fb2eb80f86a5d05c50829b4f2ad18b6587bd Parents: 0c17f54 Author: Dan Haywood <d...@haywood-associates.co.uk> Authored: Sun Jan 24 12:18:58 2016 +0000 Committer: Dan Haywood <d...@haywood-associates.co.uk> Committed: Sun Jan 24 12:18:58 2016 +0000 ---------------------------------------------------------------------- .../src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc | 2 +- .../src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc | 2 +- .../guides/_ugsec_shiro-isisaddons-security-module-realm.adoc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/isis/blob/3887fb2e/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc ---------------------------------------------------------------------- diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc index 9397bfd..ec14f68 100644 --- a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc +++ b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-ini-realm.adoc @@ -11,7 +11,7 @@ This is suitable for prototyping, but isn't intended for production use, if only The diagram below shows the Isis and components involved: -image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-ini-realm.png[width="600px"] +image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-ini-realm.PNG[width="600px"] The realm is responsible for validating the user credentials, and then creates a Shiro link:http://shiro.apache.org/static/latest/apidocs/org/apache/shiro/subject/Subject.html[`Subject`] which represents the user (for the current request). Apache Isis `Authenticator` component then interacts with the `Subject` in order to check permissions. http://git-wip-us.apache.org/repos/asf/isis/blob/3887fb2e/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc ---------------------------------------------------------------------- diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc index 0210fa7..20ac868 100644 --- a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc +++ b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isis-ldap-realm.adoc @@ -7,7 +7,7 @@ Isis ships with an implementation of http://shiro.apache.org[Apache Shiro]'s `Realm` class that allows user authentication and authorization to be performed against an LDAP server. -image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isis-ldap-realm.png[width="600px"] +image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isis-ldap-realm.PNG[width="600px"] The LDAP database stores the user/passwords and user groups, while the `shiro.ini` file is used to map the LDAP groups to roles, and to map the roles to permissions. http://git-wip-us.apache.org/repos/asf/isis/blob/3887fb2e/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isisaddons-security-module-realm.adoc ---------------------------------------------------------------------- diff --git a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isisaddons-security-module-realm.adoc b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isisaddons-security-module-realm.adoc index b57bb5f..5406b97 100644 --- a/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isisaddons-security-module-realm.adoc +++ b/adocs/documentation/src/main/asciidoc/guides/_ugsec_shiro-isisaddons-security-module-realm.adoc @@ -16,7 +16,7 @@ In order to play along, the module includes a Shiro realm, which fits in as foll The general configuration is as follows: -image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isisaddons-security-module-realm.png[width="600px"] +image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isisaddons-security-module-realm.PNG[width="600px"] where the `IsisModuleSecurityRealm` realm is the implementation provided by the module. @@ -27,7 +27,7 @@ In the configuration above user passwords are stored in the database. The modul The security module also supports a slightly more sophisticated configuration. Most organizations use LDAP for user credentials, and maintaining two separate user accounts would be less than ideal. The `IsisModuleSecurityRealm` can therefore be configured with a subsidiary "delegate" realm that is responsible for performing the primary authentication of the user; if that passes then a user is created (as a domain entity) automatically. In most cases this delegate realm will be the LDAP realm, and so the architecture becomes: -image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isisaddons-security-module-realm-with-delegate-realm.png[width="600px"] +image::{_imagesdir}security/security-apis-impl/configure-shiro-to-use-isisaddons-security-module-realm-with-delegate-realm.PNG[width="600px"] The security module has many more features than are described here, all of which are described in the module's link:https://github.com/isisaddons/isis-module-security[README]. The README also explains in detail how to configure an existing app to use this module.
