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

Posted to dev@isis.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2021/04/09 19:39:00 UTC

[jira] [Resolved] (ISIS-2534) Spring Security Integration

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

Daniel Keir Haywood resolved ISIS-2534.
---------------------------------------
    Resolution: Fixed

> Spring Security Integration
> ---------------------------
>
>                 Key: ISIS-2534
>                 URL: https://issues.apache.org/jira/browse/ISIS-2534
>             Project: Isis
>          Issue Type: New Feature
>          Components: Isis Core
>            Reporter: Andi Huber
>            Assignee: Daniel Keir Haywood
>            Priority: Minor
>             Fix For: 2.0.0-M6
>
>
> Similar to the keycloak integration, provide a new security module that delegates authorization to Spring Security.
> This affects the Viewers: Wicket, Vaadin and RO (JavaFx only optional).
> - I've only looked at Wicket.  Vaadin is still vapourware, RO we can go round the loop on.
> (see ISIS-2607) It also affects the SecMan extension, where either we need to add a new supporting module as well or alternatively simplify matters in the process, and decouple SecMan from the actual security stack in use.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)