You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2021/08/05 22:55:33 UTC

[isis] 01/01: ISIS-2483: adds missing docs on secman config

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/isis.git

commit 416dc7be67b59aafab684a0f9af05141899361f8
Author: danhaywood <da...@haywood-associates.co.uk>
AuthorDate: Thu Aug 5 23:47:36 2021 +0100

    ISIS-2483: adds missing docs on secman config
    
    (cherry picked from commit 9949db75e08d8af30bad7f194a22523a18fe408d)
---
 .../security/secman/adoc/modules/secman/pages/setting-up.adoc       | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc b/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
index d79850e..a539915 100644
--- a/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
+++ b/extensions/security/secman/adoc/modules/secman/pages/setting-up.adoc
@@ -121,9 +121,11 @@ isis:
             additional: ...                             <.>
         regular-user:
           role-name: "isis-ext-secman-user"             <.>
-      permissionsEvaluationPolicy: ALLOW_BEATS_VETO     <.>
+      permissions-evaluation-policy: ALLOW_BEATS_VETO   <.>
+      user-menu-me-action-policy: HIDE                  <.>
       user-registration:
         initial-role-names: ...                         <.>
+
 ----
 
 <.> indicates the security super-user and password
@@ -135,6 +137,8 @@ These cannot be removed (through the UI).
 These can be removed (through the UI).
 <.> indicates the name of the role that should be granted to regular users of the application.
 <.> if there are conflicted (allow vs veto) permissions at the same scope, then whether the allow wins or the veto wins
+<.> whether to HIDE, DISABLE or ENABLE the default "me" action provided by the core framework.
+Normally this should be hidden, because secman's `ApplicationUser` broadly replaces the core framework's `UserMemento`.
 <.> if self-user registration is enabled in the viewer, this defines the set of roles to be granted to said user.
 +
 This is discussed in more detail <<user-registration-aka-sign-up,below>>.