Skip to main content
Participant
May 12, 2013
Answered

What is the user scope when created with the API?

  • May 12, 2013
  • 1 reply
  • 773 views

I noticed that users created with the Adobe Connect API for my meeting/account are always listed in the Administration -> Users and Groups area.  Which probably means that a user's login is only valid for my meetings.  So if they wanted to register or join a meeting controlled by someone else, they would have to re-register or be re-created by that admin.  Is this correct?

I'm trying to confirm this so that I know how to register a user on my website.  It would be ideal if my website would register the user and also log the user in without the user having to enter a separate password (my website would generate and store the password).  If the API creates a user only for my meetings then this is not a problem.  The user will just always have to go through my website to get to the meeting.  However, if the user created by my Adobe API account can be used to access/register in another person's meetings on Adobe then this approach is not so good because the user would need to know their password.

This topic has been closed for replies.
Correct answer Jorma_at_Knox

If it is your Connect Account, then you, or the individual with the account, would be the only ones who could change their password. And for the user to do it, they would need to log into Connect Central and then My Profile and then change their PW. Or, they could use the Forgot my password link on any page that required them to log in. So, if you are passing the authentication for them to join the room, they will, in theory never see a login screen or Connect Central. Are there other Admins on your account that would be changing passwords for users?

1 reply

Jorma_at_Knox
Legend
May 13, 2013

No, the user list you see in the admin section (or any other section of Connect) is a global list for your Connect account. After you create a user account, it will be able to be used to join any meeting or view any object on Connect, that they have been given permissions to.

You could have them join as a guest, by appending the meeting room URL with '/?guest-name=John%20Doe', but then you lose the ability to track which meetings the individual attends.

I wouldn't be concerned about them having to know their password for other Connect accounts.

Participant
May 13, 2013

yea, guest registration is not an option as I need to restrict access to the meeting.

My main concern is that another Connect account holder can change the user's password.  If this ever happens, my website would have an old password and would be broken because it wouldn't be able to log the user into their meeting.  This may be a rare case, but the website will be charging for these meetings/webinars.  If the user can't get in at the time of the meeting....  i'll have a lot more problems.

I guess I'll just need to provide a way for the user to change or enter their own password. 

Thanks for the info!

Jorma_at_Knox
Jorma_at_KnoxCorrect answer
Legend
May 13, 2013

If it is your Connect Account, then you, or the individual with the account, would be the only ones who could change their password. And for the user to do it, they would need to log into Connect Central and then My Profile and then change their PW. Or, they could use the Forgot my password link on any page that required them to log in. So, if you are passing the authentication for them to join the room, they will, in theory never see a login screen or Connect Central. Are there other Admins on your account that would be changing passwords for users?