ComponentSpace

Forums



Problem with IssueInstant format


Problem with IssueInstant format

Author
Message
plouis
plouis
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)

Group: Forum Members
Posts: 4, Visits: 12
Hi,

I have a situation when my partner randomly fails to understand my AuthNRequest.

After investigation it appears it is because of an invalid IssueInstant format

Most of the time IssueInstant respects format yyyy-MM-ddTHH:mm:ss.fffZ, but sometimes it lacks the last millisecond decimale hence being of format yyyy-MM-ddTHH:mm:ss.ffZ

I joined two exemples, a good and a bad one.

Is this a bug ? If not, is there a way to force using the long format ?

Thanks,
Attachments
ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)

Group: Administrators
Posts: 3.2K, Visits: 11K
Both examples are valid. This isn't a bug in our product.
Are they expecting a trailing zero?
This is not required according to the XML schema definition of the primitive type dateTime.
http://www.w3.org/TR/xmlschema-2/#dateTime
In fact, the specification explicitly says the canonical representation should not include a trailing zero.
If the IdP is expecting a trailing zero, this sound more like a bug in their implementation.

Regards
ComponentSpace Development
plouis
plouis
New Member
New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)New Member (7 reputation)

Group: Forum Members
Posts: 4, Visits: 12
Hi,

Thanks for your quick and precise response.

They are indeed expecting a trailing zero and I'm not surprised the bug is on their side (yet again)

At least with your answer I have something solid to give them.

Anyway, if they cannot fix it on their side, is there a way to work around it on our side and still submit this trailing zero (I guess no, but I need to ask)

Thanks,
ComponentSpace
ComponentSpace
ComponentSpace Development
ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)ComponentSpace Development (4.4K reputation)

Group: Administrators
Posts: 3.2K, Visits: 11K
I'm afraid there isn't.
If they can't fix the issue please contact us and we might be able to create a workaround for you.


Regards
ComponentSpace Development
GO


Similar Topics


Execution: 0.000. 2 queries. Compression Enabled.
Login
Existing Account
Email Address:


Password:


Select a Forum....












Forums, Documentation & Knowledge Base - ComponentSpace


Search