-
Notifications
You must be signed in to change notification settings - Fork 8
Home
Coscend edited this page Sep 13, 2016
·
23 revisions
- Rooms can be displayed inside a frame in a product portal, new tab, or new window.
- The "SOAP-user” can only login into the room for collaboration. It will not have the access rights of OpenMeetings Admin-User, thereby securing OpenMeetings server from non-authorized access via the SOAP Gateway. Further, "SOAP-users” cannot login to OpenMeetings administration or change user accounts via SOAP, thereby securing confidential account data.
- Different room types can be created.
- Varying levels of moderation rights can be provided to users.
• Create a configuration file/page add OM URL add user credentials of user with soap privileges: There is only one OM-SOAP user in the OpenMeetings product. Register a user in OpenMeetings with the credentials you already have (preferably with the PHP API). Store OpenMeetings-SOAP user credentials somewhere.
- Every user of the product portal logs in to OM using that single OpenMeetings-SOAP user. Get the SessionID with the PHP API. Every user saves this authenticated sid.
- Generate a hash for the currently logged in user. (you only need some unique id for that).
call the following http://openmeetings.apache.org/openmeetings-webservice/apidocs/org/apache/openmeetings/webservice/UserWebService.html#getRoomHash(java.lang.String,%20org.apache.openmeetings.db.dto.user.ExternalUserDTO,%20org.apache.openmeetings.db.dto.room.RoomOptionsDTO)
- With that sid, create a room or use public room. Join the room with the PHP API. Create page/function you are going to call to enter OpenMeetings virtual conference room. In this function a) call /user/login (providing SOAP user credentials) b) call /user/hash (providing current user details inside "ExternalUserDTO user" parameter
- Then open or enter the OM room or watch recording by using the generated hash.