[
https://issues.apache.org/jira/browse/OPENMEETINGS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik closed OPENMEETINGS-1187.
------------------------------------------
> Send One-Time Invitation does not work if we Generate URL first.
> ----------------------------------------------------------------
>
> Key: OPENMEETINGS-1187
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1187
> Project: Openmeetings
> Issue Type: Bug
> Components: HTML5/Room
> Affects Versions: 3.0.3, 3.0.4
> Environment: Centos 6.5, Centos 7.
> Reporter: Susheel Jalali
> Assignee: Maxim Solodovnik
> Labels: features
> Fix For: 3.0.5, 3.1.0
>
>
> From a Room if a user sends an Invitation of TYPE "One-time", it only works
> as expected in case You are using "Send" or "Generate URL".
> BUT in case we first click on "Generate URL" then click on "Send" we get the
> error:
> "This invitation was already used".
> Details tested on two environments:
> 1. OpenMeetings version 3.0.3 over Centos-6.5.
> When we create an invitation using the "one-time invitation" option, then
> Generate URL, and Send it using the Send button,
> the invitation is properly sent to and received by the recipient.
> However, when the recipient uses this URL (either by clicking or by
> copy-paste) from their browser, they get the following message box error even
> the first time:
> "This invitation was already used".
> We are able to use for the same installation and recipient, the other two
> modes of invitation (Endless and Period) without any failure.
> 2. OpenMeetings-3.0.4 latest release, Centos-7
> The invitee receiving the One-Time invitation is unable to access the meeting
> room even once. It shows the error message box:
> "This invitation was already used".
> We have tested the following three scenarios:
> 1. IT Administrator sends the one-time invitation to Internal User.
> 2. IT Administrator sends the one-time invitation to External User.
> 3. External User sends the one-time invitation to Internal User.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
