Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Version 3.0. issues

Artem_M_
New Contributor I
178 Views

Hello. We try to test new version.

We installed as in instaruction. Started separated erizo, nuve, mcu, and separate example app.

But when I try to test xxx:3001 -in logs I recieve

2016-01-24 03:33:29.929  - INFO: NuveAuthenticator - [Auth] Wrong credentials

I tryed to review code, but couldn't understand what credentalsa it is need to nuve and when and how browser should give it.

All logs and configuration files are in attachment

0 Kudos
6 Replies
Chunbo_H_Intel1
Employee
178 Views

Hi Artem,

Please check the service key and id you used in the basic sample server. This is the key credentials for the NuveAuthenticator.

Another thing is that which version of Chrome you are using now?

Thanks!

Artem_M_
New Contributor I
178 Views

You are right - I had wrang id in example. Now I made id equal

config.nuve.superserviceID = '56a38c8bddd0ce1f1ae2eb09'; // default value: ''

N.API.init(
 '56a38c8bddd0ce1f1ae2eb09' 
,'c1d88bf3e2171e750ca2ecc94ae2ef00f63c137832483c2a8a725cec9e89e675a8f86d7fa481b78fa3463ce999e0abd1dc82b66db43574df80777bdef4cf312b68cb71141b8067dd82da67e604db945af668efa1a996248a75fddc003b17ca03d3cb843829ae695cb74bee019829b4f01961f2710fca11699402b098b15bff484436dad70f5401c169acedd09ce36963a8b8ef0fe54407422b09ba78549b68ba0e629de0000aefde281170a2'
, 'http://localhost:3000/');

But the result is the same:

{ realm: 'http://marte3.dit.upm.es',
  signature_method: 'HMAC_SHA256',
  serviceid: '56a38c8bddd0ce1f1ae2eb09',
  cnonce: '2c4a7ea6e1ae2d8f',
  timestamp: '1453855407897',
  signature: 'Y2E5ODM1M2Y0MGQ4ZmRjNWNlYTM5NjlkMTNiMjBhODVjMmJkOTk3M2VlZTA0ZTJhMTEyYjA1ZTZjOTRmZjE3Mg==' }
3fOHzyrh4lkpTv+KrEVwXO2ldfzR00UvjD1AH6jQgdSrKa/4AeX9Lv0hrN5xmSSLooNy3ejJWxI7rIkN/Y8BqLkZFo8XsVBQCeSvvZcY5VXs9XO8gfHCNbp7mTQahUSfmUqo2xyRPGnLGHPD1GXC6R8dN9EOoJ4gp/lXjtvxbiA=
r = MTNiZmE4ZjczNDgwOTNiMzIwNTVlZmMwNWQwZDUyNjgwYzlkN2M2NDE2NGJiZGQ1ZWY2OTczY2NlMWI2YmIyMw==
2016-01-27 03:43:27.959  - INFO: NuveAuthenticator - [Auth] Wrong credentials

 

Chrome is last version 48.0.2564.82 m.

Mozilla works in the same way, so I don't think that the browser issue

Chunbo_H_Intel1
Employee
178 Views

Hi Artem,

The NuveAuthenticator mainly checks the signature of incoming connection. So could you please check the service key in your basic server sample with the original value?

Thanks!

Artem_M_
New Contributor I
178 Views

Here is my mongo collections.  Config and sample values I posted in previous post

{  
   "name":"sampleService",
   "key":"b3e8a7f0a101597f69a2f1ef57a4a57be14a3d4b246c67299d3f65dbc0dbc272b2ed3e559887f689fd6e28e8b0e0cb97e5a3a37b8c0e17f9b67b1fcbf6f90f547793591d109665de8fd07b9e3bf396759f67e199e1ab2be470e5d3282622ef03a7faa30b2bb77c47b72d8521d949ada91f6ff75572e20e339a3a92ccbc77996a5b35fef652152fa15dd2ebf381ec0a77d0b2e32abc2272453143ac4655bd11bc460fb5fa2910f5d0301064a2",
   "encrypted":true,
   "rooms":[  

   ],
   "_id":ObjectId("56a38c8bddd0ce1f1ae2eb0a")
}{  
   "name":"superService",
   "key":"c1d88bf3e2171e750ca2ecc94ae2ef00f63c137832483c2a8a725cec9e89e675a8f86d7fa481b78fa3463ce999e0abd1dc82b66db43574df80777bdef4cf312b68cb71141b8067dd82da67e604db945af668efa1a996248a75fddc003b17ca03d3cb843829ae695cb74bee019829b4f01961f2710fca11699402b098b15bff484436dad70f5401c169acedd09ce36963a8b8ef0fe54407422b09ba78549b68ba0e629de0000aefde281170a2",
   "encrypted":true,
   "rooms":[  
      {  
         "name":"myRoom",
         "mode":"hybrid",
         "publishLimit":-1,
         "userLimit":-1,
         "mediaMixing":{  
            "video":{  
               "avCoordinated":0,
               "maxInput":16,
               "resolution":"vga",
               "multistreaming":0,
               "bitrate":0,
               "bkColor":"black",
               "layout":{  
                  "base":"fluid",
                  "custom":[  

                  ]
               }
            },
            "audio":null
         },
         "enableMixing":1,
         "_id":ObjectId("56a38ffd307277bc1c8ddc3d")
      }
   ],
   "_id":ObjectId("56a38c8bddd0ce1f1ae2eb09")
}

 

Artem_M_
New Contributor I
178 Views

That issue was fixed in 3.0.1

Chunbo_H_Intel1
Employee
178 Views

OK. Great to hear that.

Reply