[
https://issues.apache.org/jira/browse/ISIS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645609#comment-17645609
]
Daniel Keir Haywood commented on ISIS-3305:
-------------------------------------------
re: (2) keycloak - as I say, today we do have a couple of classes that during
login do claim/role/authority conversion, and for logout provide a callback for
keycloak. This code could perhaps just be moved into our
causeway-spring-security module, but there is some useful functionality there
so it need be reside somewhere.
And I am happy to maintain the docs rather than just refer folks to Baeldung,
as it takes a while (for me at least) to piece together the parts, so having
"our" procedure in one place is helpful (at least, I've found it to be helpful).
> [DISCUSS] Re-platform on top of Spring security.
> ------------------------------------------------
>
> Key: ISIS-3305
> URL: https://issues.apache.org/jira/browse/ISIS-3305
> Project: Isis
> Issue Type: Improvement
> Affects Versions: 2.0.0-M9
> Reporter: Daniel Keir Haywood
> Priority: Major
> Fix For: 2.1.0
>
>
> as per [https://the-asf.slack.com/archives/CFC42LWBV/p1670661588201299]
>
> Andi's wish list of changes is:
> # drop Shiro support
> # drop Keycloak support
> # instead fully integrate with Spring Security
> # drop SudoService
> # instead provide impersonation via a specialized login page
> # drop Wicket's .../login, .../logout
> # instead provide simple replacements under /security/... central to the
> application (not using Wicket)
> Why? Focus on one security stack and do that integration well
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
