at com.adobe.rtc.session.managers::SessionManagerAdobeHostedServices/onTicketError()[C:\work\main\connect\cocomo\src\com\adobe\rtc\session\managers\SessionManagerAdobeHostedServices.as:104]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at com.adobe.rtc.session.sessionClasses::SingleUseTicketService/onComplete()[C:\work\main\connect\cocomo\src\com\adobe\rtc\session\sessionClasses\SingleUseTicketService.as:99]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
Obtaining the authentication key seems to work properly. And I submit this key as URL-encoded String via flashVars to the SWF.
You are passing "test" as the role, when it should be a number (0-100).
I should have made it more explicit in the API (and I'll fix them for next release) but the value you pass is the numeric value expected by cocomo (passed as a string, since I am just passing it as part of the ticket)
I wish the error was more useful (it's the message from a conversion exception, and I thought I tried that ):
What did you use to get the authentication session and generate the token ? Any particular language ?
And, did you copy the account shared secret from the dev-portal to your application ?
Can you get a trace of the HTTP requests going from your client to the server ? Or send us info about your account so that I can check what's happening server-side ?
(sorry for the many questions but the stack trace doesn't really tell me much :)
You are passing "test" as the role, when it should be a number (0-100).
I should have made it more explicit in the API (and I'll fix them for next release) but the value you pass is the numeric value expected by cocomo (passed as a string, since I am just passing it as part of the ticket)
I wish the error was more useful (it's the message from a conversion exception, and I thought I tried that ):
The idea here is that only UserRoles.OWNER (which does == 100) can create new CollectionNodes in a room. Most collaboration components (Chat, SharedWhiteboard, etc) add CollectionNodes to the room when they are first run, in order to publish and subscribe data messages. Once a CollectionNode has been added to a room, it's permanently there, so subsequent users can use it without needing to be an OWNER.