[
https://issues.apache.org/jira/browse/SYNCOPE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950509#comment-17950509
]
ASF subversion and git services commented on SYNCOPE-1877:
----------------------------------------------------------
Commit 8cb85bfc95557d0367346639664581275905be83 in syncope's branch
refs/heads/4_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=8cb85bfc95 ]
[SYNCOPE-1877] Removing SAML2SPEntity and related (#1072)
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot]
<49699333+dependabot[bot]@users.noreply.github.com>
> Include SAML SP keystore and metadata in AuthModule configuration
> -----------------------------------------------------------------
>
> Key: SYNCOPE-1877
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1877
> Project: Syncope
> Issue Type: Task
> Components: console, core, wa
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 4.0.0, 4.1.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In Syncope 3.0 there is a dedicate {{SAML2SPEntity}} with its own
> persistence, REST service and Console configuration section.
> Such entity is there to hold the generated SP keystore and metadata, while
> the AuthModule configuration which generated such items is stored elsewhere.
> Also, having such items in different Console places makes difficult to work
> with it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
