Note that the encoding is base64url, not base64.
Dan
On Thursday, February 23, 2012 at 12:59 PM,
davidi...@gmail.com wrote:
>
> On 23 Feb 2012, at 20:23, Ozten wrote:
>
> > I think I've reproduced your issue as well as another.
>
> Great.
>
> >
> > Browser tools aren't great for debugging these types of apps, lots of
> > errors don't show up in error console :|
> >
>
>
> Yeah. I tried myself, but got lost in the channel...
>
> I'm watching the issue, so let me know via a comment there if there's anything I can do
>
> >
> > I'm also taking notes on developer pain points and areas we can make
> > it easier to troubleshoot as your writing a new primary.
> >
>
>
> Other than this issue, the main pain is dealing with the base64 encoded chunks, and not really knowing why one is invalid. It'd be cool to have a site you could paste the base64 chunk into and it'd validate with verbose errors. I spent a while trying to use the RS128 alg option to sign the cert, and it is (I think) the case that only RS256 is supported. Verbose errors, and the ability to test code without redeploying a server etc would be great.
>
> David
> _______________________________________________
> dev-identity mailing list
>
dev-id...@lists.mozilla.org (mailto:
dev-id...@lists.mozilla.org)
>
https://lists.mozilla.org/listinfo/dev-identity
>
>