You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@causeway.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2023/07/13 09:35:00 UTC

[jira] [Closed] (CAUSEWAY-3513) Remove the causeway-extensions-shiro-realm-ldap extension.

     [ https://issues.apache.org/jira/browse/CAUSEWAY-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood closed CAUSEWAY-3513.
-----------------------------------------

> Remove the causeway-extensions-shiro-realm-ldap extension.
> ----------------------------------------------------------
>
>                 Key: CAUSEWAY-3513
>                 URL: https://issues.apache.org/jira/browse/CAUSEWAY-3513
>             Project: Causeway
>          Issue Type: Improvement
>          Components: Ext Sec shiro-realm-ldap
>    Affects Versions: 2.0.0-RC1
>            Reporter: Daniel Keir Haywood
>            Assignee: Daniel Keir Haywood
>            Priority: Major
>             Fix For: 2.0.0-RC2
>
>
> In light of secman, this realm is for the most part redundant.  What it does is to extend Shiro's LDAP realm to also query LDAP for roles (aka groups), and to map these roles to permissions ... in other words, it adds authorisation on top of Shiro's LDAP authentication.
> However, it's much more convenient and powerful to use secman for authorisation.  We already have support (through secman's own realm with "delegate" realm capability) to configure shiro for ldap authentication, with secman for authorisation.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)