Can't authorize using devsandbox and sampleclient.html

[danil0507]

Hello

Can anyone guide me with how to solve an error

[Console] Stream opened with psdtemea.cisco.com <stream:features xmlns:stream="http://etherx.jabber.org/streams"><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>CISCO-VTG-TOKEN</mechanism></mechanisms></stream:features>

<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
           mechanism='PLAIN'>

AGRhbmlsLmJvZ29tb2xvdi5kYgBib1VJRUx2Vg==

</auth>

<failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>

<not-authorized/>

</failure>

SASL failure from server: {urn:ietf:params:xml:ns:xmpp-sasl}not-authorized

Exception during connection: <error><not-authorized xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/></error>

[Console] Stream closed.

Login and pass are right according to instructions given here:

Shared Jabber Sandbox - Cisco Developer Community

Also here are my settings. Hope someone will help.

Thanks for requesting Shared lab access. Your access information is as follows:

To download VPN client access URL:

URL: https://64.103.37.6

Username: danil.bogomolov.db

Password: boUIELvV

NOTE: If you already have the Anyconnect Clinet installed on your device, please enter the URL into the client directly and connect.

Once VPN is established, you can connect to your device with the following:

Username:

Password: cisco1234

Device:

Directory Number:

To access shared resources:

Cisco Unified Communications Manager

Name:           pub-local.psdtemea.cisco.com

Address:        10.10.20.1

Domain:         psdtemea.cisco.com

Cisco Unified Presence Server

Name:           cup.psdtemea.cisco.com

Address:        10.10.20.20

Domain: psdtemea.cisco.com

TFTP server:    10.10.20.1

Basic config was used as in example:

var demo_config = {

domain: "psdtemea.cisco.com",

maxGraphAge: 5,

unsecureAllowed: true,

atSymbolAllowed: false,

logPersistence: false,

serviceDiscoveryEnabled: false,

httpBindingURL: "http://cup02:7335/httpbinding",

httpBindingURL_secondary: "/httpbinding"

}

Please help me with this error.

Cheers

[danil0507]

Somehow after some time I was able to connect to chat room. Magic

[npetrele]

Magic is wonderful, isn't it?

I don't know if this is what happened for you, but I need to get rid of the OK buttons in my popup dialogs.  It's a UI faux pas. I frequently click OK instead of Connect in the connection dialog, and then wonder why it didn't connect. 

Anyway, I'm glad everything is working for you now. 

[danil0507]

Yeah, now all goes well and glad for your help.

Just the last thing I'm wondering how should be set up a server witch hosts chat-room. Actually is it a separate setup on Jabber server side to have testroom@muc.psdtemea.cisco.com. So should there be some separate server or setup for analog on this domen muc.psdtemea.cisco.com? and how this domain could be called?

[npetrele]

testroom@muc.psdtemea.cisco.com is really just a placeholder name for the jid (see the api docs).  There is no such server.

By the way, I could be wrong about the original problem being a script issue.  The next time you request a shared sandbox, be sure to click on Add_Jabber_SDK_for_Web and ADD_DEVICE_TO_ACTIVATE_BELOW.  I need to verify this by creating a new account, but it's probable that these options would have caused your account to be created properly.

[danil0507]

Thank you, Nicholas.

According to the api docs as I understand testroom@muc.psdtemea.cisco.com  should just be on the same domain as psdtemea.cisco.com but why it has "muc" before? I've tried different  sub domain and original (somth@pdtemea.cisco.com ) one without sub domain. And it only works with testroom@muc.psdtemea.cisco.com.

Also I'm wondering is there an opportunity to close specific chat room for all users so they wont be able to wright in this chat.

I were digging jabberwerx api and just found how to close chat-room on client side for each client by his own.

Should I create a separate topic for that?

Best Regards,

Danil

[npetrele]

Yes, it's expecting <anyroomname>@muc.psdtemea.cisco.com, but there is no separate server at muc.psdtemea.cisco.com. 

If you want to restrict access to a chat room, you can create a password for it in enterArgs.  From the docs:

enter(nick, enterArgs)

Enters this MUC room. This method enters existing rooms or creates new ones as needed. New rooms are configurable through this method's callbacks

{enterArgs} may be either a callback function or an object that may contain mapped functions and other room specific entry data like a password . If {enterArgs} is a function it is expected to match the following signature:

function callback(err) { this;    //refers to this room err;     //if entering failed, this is the jabberwerx.Stanza.ErrorInfo //explaining the failure, undefined if //entering succeeded } 

If {enterArgs} is an object it may define any of the following:

     successCallback: function() { this; //refers to this room } errorCallback: function(err, aborted) { this; //refers to this room err; //jabberwerx.Stanza.ErrorInfo aborted //Boolean Room creation was user aborted before configuration was complete } configureCallback: function() { this; //refers to this room } 

{enterArgs} may also contain a String password property that contains a plaintext password. for example:

 room.enter("foo@bar", {password: "foopass"})