November 2017
Intermediate to advanced
542 pages
14h 24m
English
The encoded payload for our access_token has been encoded with a private key by the authorization server, as seen in the following code:
iM5BqXj70ET1e5uc5UKgws1QGDv6NNZ4iVEHimsp1Pnx6WXuFwtpHQoerH_F- pTkbldmYWOwLC8NBDHElLeDi1VPFCt7xuf5Wb1VHe-uwslupz3maHsgdQNGcjQwIy7_U- SQr0wmjcc5Mc_1BWOq3-pJ65bFV1v2mjIo3R1TAKgIZ091WG0e8DiZ5AQaseYy43ofUWrJEXok7kUWDpn SezV96PDiG56kpyjF3x1VRKPOrm8CZuylC57wclk- BjSdEenN_905sC0UpMNtuk9ENkVMOpa9_Redw356qLrRTYgKA-qpRFUp C-3g5CXhCDwDQM3jyPvYXg4ZW3cibG-yRw
The following is pseudo code for the creation of a JWT signature:
var encodedString = base64UrlEncode(header) + "."; encodedString += base64UrlEncode(payload); var privateKey = “[-----PRIVATE KEY-----]”; var signature = SHA256withRSA(encodedString, ...
Read now
Unlock full access