• Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
brainCloud Forums

Error 40316 on authenticate

Scheduled Pinned Locked Moved APIs
s2sauthentication
3 Posts 2 Posters 498 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Benjamin Maison
    wrote on last edited by Benjamin Maison
    #1

    Hello,

    I'm posting here because I'm out of idea on this issue.
    I'm trying to establish a session based server to server connection, but I'm receiving a 40316 error code with the following message :

    Processing exception (bundle): Missing app ID in nonauthenticated request
    

    I'm using the following json as input :

    {
    	"packetId":0,
    	"appId":"XXXX",
    	"messages":
    	[
    		{
    			"service":"authenticationV2",
    			"operation":"AUTHENTICATE",
    			"data":
    			{
    				"appId":"XXXX",
    				"serverName":"####",
    				"serverSecret":"SSSS"
    			}
    		}
    	]
    }
    

    According to this link : https://getbraincloud.com/apidocs/portal-usage/using-postman-with-s2s/
    it seems that the json is properly formed.
    I also tried to rename the 'appId' to 'gameId' but in vain. (See https://getbraincloud.com/apidocs/apiref/#s2s-authentication)
    Any idea what I'm doing wrong ?
    Thank you for your time

    Note : We run on R4.14.0-8281

    P 1 Reply Last reply
    0
  • P Offline
    P Offline
    Panagiotis Milios
    replied to Benjamin Maison on last edited by
    #2

    @benjamin-maison I think the appId field below the packetId field is obsolete. The error code you're getting is for an invalid app id. Check if it's the correct one. Also, have you registered your server with the proper app id?

    B 1 Reply Last reply
    0
  • B Offline
    B Offline
    Benjamin Maison
    replied to Panagiotis Milios on last edited by
    #3

    @panagiotis-milios Thank you for your response, appreciate your time !
    I solved the issue :
    The url I was using was wrong, more precisely I was using the wrong servlet :
    I was using

    /dispatcherv2
    

    while I was supposed to use

    /s2sdispatcher.
    

    I also want to point out that you are right about the "appId" below the "packetId", it is not needed.
    Thank you, I hope this thread will help anyone encountering this problem !

    1 Reply Last reply
    1
  • Paul WinterhalderP Paul Winterhalder moved this topic from S2S APIs on

  • Login

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Solved
  • Unsolved
  • Users