Skip to main content
May 14, 2012
Question

Guestname coming from session, not from parameter, and it's URL-encoded. Need it decoded.

  • May 14, 2012
  • 1 reply
  • 875 views

We have a hosted account for Adobe Connect. When users want to enter a room, they go to a URL like this:

http://connectpro12345678.na5.acrobat.com/rereview/?launcher=false&guestName=John%20Smith

This drops them into the meeting room, but the name is listed under Participants as

John%20Smith

rather than the desired John Smith.

I've determined that the URL-encoded name is coming from the session, because when I deleted the BREEZESESSION cookie and hit the meeting room directly, using a URL like:

https://connectpro12345678.adobeconnect.com/_a963369417/rereview/?launcher=false&guestName=Michael%20Van%20Kleeck

the guest name is displayed appropriately.

How can I force Connect to either decode the guestname or to use the guestname from the parameter, rather than the session?

Thanks!

-Michael

    This topic has been closed for replies.

    1 reply

    Jorma_at_Knox
    Legend
    May 14, 2012

    You shouldn't be using the naX.acrobat.com URLs. These URLs are redirecting to the new adobeconnect.com URLs, which may be where you are seeing the issues. You shouldn't need to use your account ID (_a963369417) so your links should look like: http://connectpro12345678.adobeconnect.com/review/?launcher=false&guestName=John%20Smith

    May 14, 2012

    Thanks Jorma. That's exactly the problem. When we create new meetings and use the URL supplied, the guestname works as expected. The old URL's came from late 2010, which is the last time we were working on this feature.

    It also seems that launcher=false is no longer necessary.

    Jorma_at_Knox
    Legend
    May 14, 2012

    yeah, the launcher=false is only needed if you want viewers to not use the add-in. If it doesn't make a difference, then drop it.