syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-1117) Make it more obvious that the jwsKey needs to be changed
Date Thu, 22 Jun 2017 16:09:00 GMT

    [ https://issues.apache.org/jira/browse/SYNCOPE-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059608#comment-16059608
] 

ASF subversion and git services commented on SYNCOPE-1117:
----------------------------------------------------------

Commit a4f351196912442cd54b2e4329d952cd9855ea34 in syncope's branch refs/heads/master from
[~coheigea]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=a4f3511 ]

[SYNCOPE-1117] - Add a "DefaultCredentialChecker" to log a warning if the default JWS key
is being used


> Make it more obvious that the jwsKey needs to be changed
> --------------------------------------------------------
>
>                 Key: SYNCOPE-1117
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1117
>             Project: Syncope
>          Issue Type: Improvement
>          Components: archetype, core, documentation
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0.4, 2.1.0
>
>
> This task is to make it more obvious that the "jwsKey" property needs to be changed.
This involves:
> a) Update the maven archetype and the installer to ask for a "jwsKey" value.
> b) Update the docs for the installer, standalone and deb versions to make it clear that
the "jwsKey" value needs to be changed. 
> c) Print a warning in the logs if we detect that the default key is being used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message