The switch to using JDK8's new date / time APIs caused a minor change in behavior in Rest2Ldap which may cause problems in some client applications. In particular, timestamps expressed using LDAP's generalized time syntax are converted to ISO 8601 using java.time.OffsetDateTime#toString which has the following documented behavior:
Unfortunately some clients cannot parse the truncated format. In addition, it has been suggested that we should generate a string representation that can be reliably compared, but that's only possible if the timezone is normalized to UTC and trailing nano-seconds are always included. I don't think we should do that since the conversion is losing information (the original time zone) - clients should take care to compare values properly.
Acceptance criteria: this issue can be closed once the generated ISO 8601 string no longer truncates the seconds field.