Expiration date set in AD causes year 10000 error

[elonden]

The "ldap3/protocol/formatters/formatters.py" on line 118 throws me an error when a expiration date in AD is set to 31/12/9999. As any timezone east of GMT this will roll over into year 10000 this try will show a "ValueError: year 10000 is out of range".

Unfortunately there is not much we can do on the AD side as the accounts get synced from another source which does not allow a non-expiration date and uses that 31/12/9999 as a "work around". So even if we would set the expiration date one day earlier, it would be back where it was on the next re-sync cycle.

Any idea how to get around this?

cheers
Erwin