Skip to content

Conversation

@fcv-iteratorIt
Copy link
Contributor

No description provided.

Copy link
Contributor

@augusthjerrild augusthjerrild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might have misunderstood it. But if i give my user an expire date from 2 days ago, i would expect that the user could not login. Right now that is possible. It might be an issue in the backend :)

Copy link
Contributor

@augusthjerrild augusthjerrild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really nice.

Only thing I observe, is, that if a user has been deactivated because the date is expired, and i then change the deactivationDate to something later, then it still stands as deactivated. I think I would expect the user to be activated again. Instead I have to do it manually. It might be fine, but this is an observation and we might consider what should be the best solution :-)

@fcv-iteratorIt fcv-iteratorIt merged commit ca8fdd0 into stage Jun 13, 2025
3 checks passed
@fcv-iteratorIt fcv-iteratorIt deleted the feature/IOT-46-Time-limited-access branch June 13, 2025 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants