Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit f5cdc4e

Browse files
committed
Project site updated, again.
1 parent 8136c05 commit f5cdc4e

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

‎index.html‎

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,7 @@
214214
</p>
215215
<p class="section">
216216
JSON Web Keys are JSON data structures representing cryptographic keys. The RFC 7517 (JSON Web Key) defines only the common parameters such like the mandatory
217-
"kty" (the key type identifying the cryptographic family of the key) or the optional "kid" (the key id which may be used by applications to look up, for instance, the key
217+
"kty" (the key type identifying the cryptographic family of the key) or the optional "kid" (the key id which may be used by an application to look up, for instance, the key
218218
required to validate a digital signature) and leaves the parameters specific to certain cryptographic algorithms to RFC 7518 (JSON Web Algorithms).
219219
There are further RFCs describing the usage of additional algorithms like EdDSA and their respective specific keys not covered by RFC 7518.
220220
</p>
@@ -431,8 +431,8 @@
431431
scenario the authenticity of a particular Open ID Connect Provider can be established by HTTPS and accompanying certificate chains.
432432
</p>
433433
<p class="section">
434-
You don't have to consult the <span class="code">JOSEHeader</span> class if you use the Fluent API to create JSON Web Signatures because then the JOSE Header will be inferred
435-
from your input. But it might be useful if you must provide a custom JOSE header, e.g. by directly using the <span class="code">JWSSigner</span>.
434+
You don't have to consult the <span class="code">JOSEHeader</span> class if you use the <aclass="content" href="#fluent-api">Fluent API</a> to create JSON Web Signatures because then
435+
the JOSE Header will be inferred from your input. But it might be useful if you must provide a custom JOSE header, e.g. by directly using the <span class="code">JWSSigner</span>.
436436
</p>
437437
<p class="section">
438438
This distribution presently supports the following JOSE header parameter
@@ -606,7 +606,7 @@
606606
.payload(payload)
607607
.sign();</p>
608608
<p class="section">
609-
The textual representation of the JWS Compact Serialization are three Base64Url encoded parts separated by two dots, e.g.:
609+
The textual representation of the JWS Compact Serialization are three Base64-URL encoded parts separated by two dots, e.g.:
610610
</p>
611611
<p class="code">eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImRlOGQyOTA3LTk5YjAtNDQ5Zi04MzVjLTY5ZWZhNjc1YjBiNSIsImp3ayI6eyJrdHkiOiJFQyIsImNydiI6IlAtMjU2IiwieCI6ImhjTUF3X0JxUXN2NDU3RHh2UnprQVJXRDl4MWVsTm9EX3RTREwtcmVlUTAiLCJ5IjoiVmFjM0M4ejlscXdDNmdxbTl1bVNLb0tfRnE0OGU1MnJyd2xqeF81SFloMCJ9fQ.eyJpc3MiOiJPcGVuSURDb25uZWN0LVByb3ZpZGVyIiwiZXhwIjoxNzQ0NzMyOTk2LCJhdWQiOiJQcm90ZWN0ZWQgQXBwIiwianRpIjoiZTU3NWZhNjgtNGQyNC00Mzk4LWEyYzgtODc0MzJkOGFhNTdiIiwibmFtZSI6IlRpbmEgVGVzdGVyIiwiZW1haWwiOiJ0aW5hLXRlc3RlckB4eXouYWJjIiwicm9sZXMiOlsiYXBwLXVzZXIiLCJhcHAtdGVzdGVyIl19.XvBeAVcUHMvZj1f2xw4WRB52_Ii721u5DpGGqbRwpim4xkXWcppVdhYMb3xyLbJzK9ZoR3mgTJ8ZFx_eNpui9A</p>
612612
<p class="section">
@@ -829,7 +829,7 @@
829829
}
830830
}""";</p>
831831
<p class="section">
832-
The JSON string referenced by <span class="code">secret</span> contains the Base64Url encoded key bytes:
832+
The JSON string referenced by <span class="code">secret</span> contains the Base64-URL encoded key bytes:
833833
</p>
834834
<p class="code">JsonObject keyMaterial;
835835
try (StringReader stringReader = new StringReader(strKeyMaterial);
@@ -942,7 +942,8 @@
942942
<p class="section">
943943
Both <span class="code">r</span> and <span class="code">s</span> can be appended and then Base64-URL encoded to obtain the actual signature:
944944
</p>
945-
<p class="code">System.arraycopy(r, 0, signature, 0, r.length);
945+
<p class="code">byte[] signature = new byte[64];
946+
System.arraycopy(r, 0, signature, 0, r.length);
946947
System.arraycopy(s, 0, signature, 32, s.length);
947948
String encodedSignature = JWSBase.encode(signature);
948949
assert Objects.equals(encodedSignature, "DtEhU3ljbEg8L38VWAfUAqOyKAM6-Xx-F4GawxaepmXFCgfTjDxw5djxLa8ISlSApmWQxfKTUJqPP3-Kg6NU1Q");</p>

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /