Re: [OAUTH-WG] JWS encoding Appendix A

2013-06-05 Thread Antonio Sanso
h-boun...@ietf.org<mailto:oauth-boun...@ietf.org> [mailto:oauth-boun...@ietf.org] On Behalf Of Antonio Sanso Sent: Wednesday, June 05, 2013 3:27 PM To: oauth@ietf.org<mailto:oauth@ietf.org> WG Subject: [OAUTH-WG] JWS encoding Appendix A Hi *, while testing my encoding routine ag

Re: [OAUTH-WG] JWS encoding Appendix A

2013-06-05 Thread Justin Richer
121, 112, 34, 58, 34, 74, 87, 84, 34, 44, 13, 10, 32, 34, 97, 108, 103, 34, 58, 34, 72, 83, 50, 53, 54, 34, 125] Best regards Axel *From:*oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] *On Behalf Of *Antonio Sanso *Sent:* Wednesday, June 05, 2013 3:27 PM *To:* oauth@ietf.org WG *Subj

Re: [OAUTH-WG] JWS encoding Appendix A

2013-06-05 Thread Axel.Nennker
PM To: oauth@ietf.org WG Subject: [OAUTH-WG] JWS encoding Appendix A Hi *, while testing my encoding routine against JWS I spot a difference between my encoding and the one in the spec. More specifically I am referring to Appendix A.1.1 [0] of the JWS spec. Now it could easily be that the

[OAUTH-WG] JWS encoding Appendix A

2013-06-05 Thread Antonio Sanso
Hi *, while testing my encoding routine against JWS I spot a difference between my encoding and the one in the spec. More specifically I am referring to Appendix A.1.1 [0] of the JWS spec. Now it could easily be that the library I wrote is wrong but it works fine with the encoding in the JWT sp