Closed miskopo closed 4 months ago
I believe the issue related to setting time in krb5 is related to this one. Basically, each request to change sends the time set to hard-coded value, but I was unable to figure out where this value is coming from.
{
"method": "user_mod",
"params": [
[
"armadillo"
],
{
"version": "2.251",
"krbprincipalexpiration": "20240716220016Z"
}
]
}
which corresponds to time 00:00
, however the date is skewed by 1 (the value is correct after the reload)
{
"method": "user_mod",
"params": [
[
"armadillo"
],
{
"version": "2.251",
"krbprincipalexpiration": "20240719220016Z"
}
]
}
again, date moved by one day and time set to 00:00
My investigation led me to several possible culprits.
src/utils/utils.tsx
- there is a discrepancy in behaviour of setUTCHours
nad setHours
.src/components/Form/DateTimeSelector.tsx
- onTimeChange is not triggering/processing the time correctly
In User details, when modifying just the time part of the datetime fields (e.g.
Kerberos principal expiration (UTC)
), theSave
button doesn't enable.