I believe not.
But it's not heavy to do it by yourself.
For example..
Create a new field based on the expiry date.
Set the date for it.
In Dev Client you can write some code before the RTC will open.
Here you can check today or workdate with your new field and the user.
If the date is greater than the new field and new fiel not equal null you can generate an error message that the user password is expiried or automatic set the booleon "user must change password at next login" or something else....
Maybe you can check the C/AL functions:
SETUSERPASSWORD(USID, Password)
CHANGEUSERPASSWORD(OldPassword, NewPassword) //- Only for current user!
Comments
I believe not.
But it's not heavy to do it by yourself.
For example..
Create a new field based on the expiry date.
Set the date for it.
In Dev Client you can write some code before the RTC will open.
Here you can check today or workdate with your new field and the user.
If the date is greater than the new field and new fiel not equal null you can generate an error message that the user password is expiried or automatic set the booleon "user must change password at next login" or something else....
Maybe you can check the C/AL functions:
SETUSERPASSWORD(USID, Password)
CHANGEUSERPASSWORD(OldPassword, NewPassword) //- Only for current user!
Hope this helps.
came