You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2019/12/12 07:22:00 UTC
[jira] [Assigned] (SYNCOPE-1525) Documentation indicates sharing
private key, hiding public key
[ https://issues.apache.org/jira/browse/SYNCOPE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò reassigned SYNCOPE-1525:
-----------------------------------------------
Assignee: Francesco Chicchiriccò
> Documentation indicates sharing private key, hiding public key
> --------------------------------------------------------------
>
> Key: SYNCOPE-1525
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1525
> Project: Syncope
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.1.5
> Reporter: Michael Power
> Assignee: Francesco Chicchiriccò
> Priority: Major
>
> The reference guide (found at [https://syncope.apache.org/docs/2.1/reference-guide.html]) references JWT asymmetric key signing, but when talking about the keys, it mentions that the private key should be shared and the public key should remain secret. This is the opposite of what is generally practiced. I am assuming that this is a typo and that public and private should be switched.
>
> Here is the wording:
> {quote}This configuration requires to specify a key pair: the former key value, said _private_, must be shared with clients, while the latter key value, said _public_, must be kept secret for internal Core usage.
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)