[
https://issues.apache.org/jira/browse/OPENMEETINGS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Hepp updated OPENMEETINGS-1846:
-------------------------------------
Attachment: db_invitation.txt
> Need a way to invalidate "endless" invatation
> ---------------------------------------------
>
> Key: OPENMEETINGS-1846
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1846
> Project: Openmeetings
> Issue Type: Improvement
> Components: Invitation
> Affects Versions: 4.0.2
> Environment: UBUNTU 16.04VM OM4.0.2
> Reporter: Aaron Hepp
> Assignee: Maxim Solodovnik
> Priority: Minor
> Labels: features
> Attachments: db_invitation.txt, invitation.doc
>
>
> Currently there is no way to invalidate an endless invitation once the user
> has the link. Easiest way I can see is by "updating" the row in the database
> instead of creating a new one. You can either create a new invitation with a
> expired date/time or create it as endless and just not publish the invite
> link to the user. That way the previous link hash is not valid in the
> database and the user does not have the new link.
> Currently each time you create an invitation, it creates a new row in the
> database with a new id (see image). Instead of the new row update existing
> columns with new data:
> IF invitee_id AND room_id EXIST UPDATE hash AND updated (sorry not a database
> guy to know exact syntax to use)
> This will allow you to invalidate an invite for the user in one room while
> keeping the users invite for another room still valid. If the user was no
> longer allowed in any room, then just delete the user and link becomes
> invalid as it can not find invitee_id
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
