You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/02/18 16:15:00 UTC
[jira] [Commented] (ISIS-2534) Spring Security Integration
[ https://issues.apache.org/jira/browse/ISIS-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286572#comment-17286572 ]
ASF subversion and git services commented on ISIS-2534:
-------------------------------------------------------
Commit 809d5d628e3679ef955977a65d0f9396cdeabeef in isis's branch refs/heads/ISIS-2534-spring_sec from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=809d5d6 ]
ISIS-2534: add Spring Security module (just a stub)
> 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: Andi Huber
> 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).
> 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)