A user must be an Administrator to create a Adobe Connect meeting, which means the user is a member of the Meeting Hosts group. In the response from principal-list, this group has type=live-admins.
A meeting can be public, protected, or private, and to create each, you need to set a specific combination of principal-id and permission-id:
Public, equivalent to Anyone who has the URL for the meeting can enter the roomprincipal-id=public-access&permission-id=view-hidden
Protected, equivalent to Only registered users and accepted guests can enter the roomprincipal-id=public-access&permission-id=remove
If a meeting is protected, registered users invited as meeting participants can enter by clicking the meeting room URL and logging in. Users who are not invited can log in as guests. The meeting host receives a guest’s request to enter (known as knocking) and can accept or decline.
Private, which is equivalent to Only registered users and participants can enter. The login page does not allow guests to log in.principal-id=public-access&permission-id=denied
When you select the option Anyone who has the URL, your room is publicly available. Any content uploaded to your room, is also publicly available. Any user who has the URL can access the uploaded content without your knowledge.
Call principal-list to check that the user creating the Adobe Connect meeting is a member of the live-admins group:
<sco folder-id="2006258750" lang="en" account-id="624520" type="meeting" icon="meeting" sco-id="2007184134" version="0"> <date-begin>2006-10-01T09:00</date-begin> <date-end>2006-10-01T17:00</date-end> <url-path>/october/</url-path> <name>October All Hands Meeting</name> </sco>
Call permissions-update to make the meeting public. Use the sco-id of the meeting as the acl-id: