API - Creating a second meeting with a blank meeting ID overrides the first meeting #1222

Closed
bigbluebutton-issue-import opened this Issue Aug 12, 2015 · 6 comments

Projects

None yet

3 participants

@bigbluebutton-issue-import

Originally reported on Google Code with ID 467

This is an issue discovered by Ian Bothwell. Below is his description of
the problem:

Description:

Create Meeting API call when invoked without a meetingID does not create a
a dynamically new meetingID and subsequent calls to create without a
meetingID overwrite the previously created sessions attributes ( ie.
meetingToken, passwords,... ).

And example would be:

   1. Call create API without meetingID ( meetingID, attendee password,
moderator password all left empty )
   2. meetingToken is returned ( meetingID field is returned empty )
   3. Generate Join Links for both moderator and attendees ( both work at
this point when visited )
   4. Call create API again without meetingID ( meetingID, attendee
password, moderator password all left empty )
   5. meetingToken is returned ( meetingID field is returned empty )
   6. Try clicking the previous links generated by the first create API
invocation. User now experiences an error telling them that their password
is invalid.


Http Debug Trace:

First Invocation Request:

http://174.129.10.185/bigbluebutton/api/create?name=Ian%20Bothwell&checksum=a54e523235208f9236f0d76dab1f46b880bab834

Response:
<response>
<returncode>SUCCESS</returncode>
<meetingToken>79bcf3aa-ee3a-4c21-a0b7-f91c5f729033</meetingToken>
<meetingID></meetingID>
<attendeePW>05lssmhz</attendeePW>
<moderatorPW>tcm7r5e4</moderatorPW>
<messageKey></messageKey>
<message></message>
</response>

Moderator Join Link: 
http://174.129.10.185/bigbluebutton/api/join?fullName=bob&meetingID=&password=tcm7r5e4&checksum=a17fcc1f7d4b929de8a6f891ac5429068c22a7a3
Participant Join Link: 
http://174.129.10.185/bigbluebutton/api/join?fullName=jane&meetingID=&password=05lssmhz&checksum=fba325bfeacb52c9a3974595f9815093cedcacfe

Second Invocation Trace:

http://174.129.10.185//bigbluebutton/api/create?name=Ian%20Bothwell&checksum=a54e523235208f9236f0d76dab1f46b880bab834

Response:
<response>
<returncode>SUCCESS</returncode>
<meetingToken>d0f7f457-c61a-47a2-ae5c-109bb89343e5</meetingToken>
<meetingID></meetingID>
<attendeePW>0nocgt0o</attendeePW>
<moderatorPW>pfynolb2</moderatorPW>
<messageKey></messageKey>
<message></message>
</response>

Moderator Join Link: 
http://174.129.10.185/bigbluebutton/api/join?fullName=randy&meetingID=&password=pfynolb2&checksum=8cf66a5d5cb33caebcd47257619fb90eab62d266
Participant Join Link:
http://174.129.10.185/bigbluebutton/api/join?fullName=michelle&meetingID=&password=0nocgt0o&checksum=03161d1bdd37cadd4851117f3b967a70fd9efead


Conclusion:

I assume that this is not the desired behaviour. In this case I would
assume that the API should return a new unique meetingID that upon
subsequent calls to the create API should not be overridden.

Reported by ielashi on 2010-04-02 15:10:00

@bigbluebutton-issue-import
Also, look at Issue #473 - we should kill both birds with one stone.

Reported by jeremythomerson on 2010-04-08 01:42:45

  • Labels added: Milestone-Release0.7, Component-API
@bigbluebutton-issue-import
Well, I was three birds with one stone ;)

Have a look at:
http://code.google.com/p/bigbluebutton/issues/detail?id=468&q=activity%20monitor&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Component%20Summary

Reported by ielashi on 2010-04-08 02:16:47

  • Status changed: ``
  • Labels removed: Type-Defect, Priority-Medium, Milestone-Release0.7, Component-API
@bigbluebutton-issue-import

Reported by ffdixon on 2011-02-06 15:00:41

  • Labels added: Type-Defect, Priority-Medium, Component-API
@bigbluebutton-issue-import
The API now creates an internal meetingid. When a call to the same meeting id is done,
the user gets put the the same meeting.

Reported by ritzalam on 2012-03-28 18:33:06

  • Status changed: Fixed
  • Labels added: Milestone-Release0.8
@bigbluebutton-issue-import
Wow! That issue took a little bit longer to close than I expected :D

Reported by ielashi on 2012-03-29 06:17:01

@bigbluebutton-issue-import
We're very persistent :-)

Reported by ffdixon on 2012-03-29 12:53:03

@kepstin kepstin modified the milestone: Release 0.8 Aug 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment