Closed henry0715-dev closed 2 months ago
I'll work with option 2.
I think https://github.com/aicers/review-web/issues/41 suggests option 2, and I agree with your choice.
We plan to proceed after the #100 issue is processed, so we will close the current issue.
Pre-work is required in "Review-Database" to add password-related logic in "Review-WEB". The account policy to be added is as follows: b"password expiration period".
expiry_period_in_secs This seems to be being used as a value for the expiration of the login session. I need to save a different value so that you can check the password expiration date.
We need to implement CRUD functionality for the value of "password expiration period." To achieve this, it is necessary to determine whether to add a new field to the AccountPolicy or to declare a separate structure for this purpose.
I would like to ask for your opinion on which approach, between option 1 and option 2, would be preferable for implementation. Henry is scheduled to carry out this task.
reference https://github.com/aicers/review-web/issues/41 https://github.com/aicers/review-web/issues/42