jsrsasign | Sign JavaScript Library ) is an opensource | TLS library

crypto-js doesn't implement AES-CMAC algorithm, so you are getting a different result. There's one that i found node-aes-cmac. Using this, i got the expected output.

Code for refernce:

I have almost test every method in package jsrsasign, but still not found anything useful.

So I look outside the box and think, the X509V3 Subject Key Identifier(SKI) was produced by the default sha1 hash algo. However, what we have done in the hyperledger/fabric, defined that the hash algo to be sha256. So what if the jsrsasign has made that hash algo hardcoded with sha1? (This is a guess, please correct me if I am wrong.)

With that thought, I have tried on another package node-forge, which just solved my problem.

Here is the demo:

As you can see on https://status.npmjs.org, 4 packages are down at this moment.

They've fixed the issue but we need to wait for CDN world propagation.

Don't update your packages or install new one to fix this.

EDIT: not working yet in Europe at 14:34 UTC

Youcould match the begin certificate part, then capture in a group matching all lines that do not start with ----- using a negative lookahead (?!-----) and after that match the end certificate part.

I was able to solve this.

My private key had escaped white space characters in it (\n,\t)

I opened up google chrome dev tools and just saved it to a variable with template literals and console logged it out to get a properly formatted key.

Another option may just to do that in Postman as well.

After that, it worked.

Published Collection: https://documenter.getpostman.com/view/8140651/SWECYFyf?version=latest

• The return-value of KJUR.jws.JWS.sign consists of three portions separated by a dot. The first part is the Base64url-encoded JSON-string sHeader, the second part is the Base64url-encoded JSON-string sPayload and the third part is the Base64url-encoded signature. The data to be signed consist of the first two portions including the dot separating the two portions. RS256 means that SHA256 and RSA with RSASSA-PKCS1-v1_5 padding is used for the signature. This can also be easily verified online, e.g. here, whereby SHA256withRSA is to be selected as the algorithm.

• openssl_sign also uses RSA with RSASSA-PKCS1-v1_5 padding and therefore creates the same signature with SHA256, assuming the same key and the same data to be signed are applied.

• jsrsasign uses Base64 url-encoding (RFC4648, sect. 5), while PHP (or more precisely the base64_encode-method) uses standard Base64-encoding (RFC4648, sect. 4), which most likely is one cause of the issue. This means that the encoding in the current PHP-code must be changed to Base64url, e.g. here.

• Of course, the underlying JSON-strings in the PHP-code ($header, $payload and $token) must also be identical to their counterparts in the JavaScript-code, otherwise the signature will differ. Since the PHP-code is incomplete, this cannot be checked and could be another cause of the problem.

The cause is a different format. Microsoft expects the format r|s while your signature is specified in the ASN.1-format (which is explained in the context of ECDSA here):

iOS has till a lot of open parts about PWAs support. Do you get any console errors? Is web app manifest correctly seen via the browser?

Which version of Safari are you using? On can I use web site you can verify the Safari version that supports service workers.

You can re-implement the Java password hashing using the standard Node.js crypto module: