• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 96 subscribers
  • Views 518 views
  • Users 0 members are here
Options
Related

The API portal enforces 'End of Day' time on all product requests/renewals

Niels de Groot
1 month ago

The DateTimeDetail for ValidUntil@ShoppingCartItem/PersonWantOrg is locked to 'End of day'
The new portal enforces this setting by not allowing an user defined end time on the product request/renewal
For details see: https://github.com/OneIdentity/IdentityManager.Imx/issues/255

In the webdesigner portal you where allowed to set the exact time you wanted a product request to end (ValidUntil)

So based on the new portal behaviour and the locked schema setting on DateTimeDetail of ValidUntil@ShoppingCartItem/PersonWantOrg.

I can only conclude that setting an user defined end time on product request/renewal is no longer supported.

Can someone from Quest clarify this please?

Thank you,
Niels

Top Replies

Parents
  • 0 1 month ago

    This is correct. The reason this was done was that we ran into issues with the data formats. In the API, there is an additional layer of JSON (de-)serialization of dates to worry about. This would need to made _very_ robust when you have both dates without time-of-day (which need to be patched to end-of-day) and dates with time-of-day (which must not be patched).

    So the reason is technical, but it is on the backlog to make this more flexible.

Reply
  • 0 1 month ago

    This is correct. The reason this was done was that we ran into issues with the data formats. In the API, there is an additional layer of JSON (de-)serialization of dates to worry about. This would need to made _very_ robust when you have both dates without time-of-day (which need to be patched to end-of-day) and dates with time-of-day (which must not be patched).

    So the reason is technical, but it is on the backlog to make this more flexible.

Children
No Data