relevantDate field improperly populated about jpasskit HOT 4 CLOSED

Thanks for your report.
Should be fixed now.
I've pushed a new snapshot to our repository so that you'll get the fixed version as soon as your maven fetches it.

from jpasskit.

Thanks for the quick update! Unfortunately I'm afraid the date still doesn't work. The bugs do not appear to be on the jpasskit side, but may need to be dealt with anyways if relevantDate is to be supported. Apple claims it expects a W3C formatted date (ISO 8601): http://www.w3.org/TR/NOTE-datetime.

Actual:
"relevantDate": "2012-10-04T05:00:00.000+0000"

"Expected":
"relevantDate": "2012-10-04T05:00:00+00:00"

There are two bugs:

1. Apple does not allow seconds in decimal notation. The W3C specification says it's OK, but passes won't load.
2. Java uses the RFC 822 spec for it's timezone format, which is incorrect according to the W3C spec. Timezone must have a colon between the hours and seconds.

Perhaps down the road it may be best to allow the user to supply a date format somehow? Just a thought.

Thanks again!

from jpasskit.

Damn. You are right.

Allowing a custom date format isn't such a good idea as the format should be exactly what Apple defined it. Too much room for errors.

The PKSigningUtil is meant to be a shortcut for the people who just want to get going. They have always the possibility to just use the basic classes and do it on their own. Or just use some of its functionality while doing other parts differently. That's why I kept the other classes as clean and basic as possible.

Should be fairly easy to fix, though. Just a custom date formatter for jackson.

from jpasskit.

Nice! Worked for me. A simple timezone test also worked. Cheers.

from jpasskit.