[ https://issues.apache.org/jira/browse/SYNCOPE-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994319#comment-16994319 ]
ASF subversion and git services commented on SYNCOPE-1525: ---------------------------------------------------------- Commit 3869e117bd9c47290e668d939d3d47d4e591e22c in syncope's branch refs/heads/2_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3869e11 ] [SYNCOPE-1525] Fixing public / private wording as suggested > 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.0.14, 2.1.5 > Reporter: Michael Power > Assignee: Francesco Chicchiriccò > Priority: Major > Fix For: 2.0.15, 2.1.6, 3.0.0 > > > 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)