Identifying unique browsers with a Spring backend and React frontend












0















I am developing a web-based multiplayer boardgame, using a Spring/Java/Maven backend and React/JavaScript frontend. Since the game is turn-based, I want to identify each individual player so that I can ensure only the active player can click and I can send individual messages to each player.



We have been looking at using Spring Security, but we have been having issues with this. Identifying clients with users & passwords seems like overkill as we are not concerned about security, is there a better approach? Essentially, what is the best way to manage distinct users and then serve them with individual messages/actions?










share|improve this question























  • Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

    – brk
    Nov 21 '18 at 14:06











  • session cookie?

    – epascarello
    Nov 21 '18 at 14:09











  • @brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

    – saeched
    Nov 21 '18 at 14:09











  • @epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

    – saeched
    Nov 21 '18 at 14:10






  • 1





    @saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

    – brk
    Nov 21 '18 at 14:10


















0















I am developing a web-based multiplayer boardgame, using a Spring/Java/Maven backend and React/JavaScript frontend. Since the game is turn-based, I want to identify each individual player so that I can ensure only the active player can click and I can send individual messages to each player.



We have been looking at using Spring Security, but we have been having issues with this. Identifying clients with users & passwords seems like overkill as we are not concerned about security, is there a better approach? Essentially, what is the best way to manage distinct users and then serve them with individual messages/actions?










share|improve this question























  • Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

    – brk
    Nov 21 '18 at 14:06











  • session cookie?

    – epascarello
    Nov 21 '18 at 14:09











  • @brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

    – saeched
    Nov 21 '18 at 14:09











  • @epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

    – saeched
    Nov 21 '18 at 14:10






  • 1





    @saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

    – brk
    Nov 21 '18 at 14:10
















0












0








0








I am developing a web-based multiplayer boardgame, using a Spring/Java/Maven backend and React/JavaScript frontend. Since the game is turn-based, I want to identify each individual player so that I can ensure only the active player can click and I can send individual messages to each player.



We have been looking at using Spring Security, but we have been having issues with this. Identifying clients with users & passwords seems like overkill as we are not concerned about security, is there a better approach? Essentially, what is the best way to manage distinct users and then serve them with individual messages/actions?










share|improve this question














I am developing a web-based multiplayer boardgame, using a Spring/Java/Maven backend and React/JavaScript frontend. Since the game is turn-based, I want to identify each individual player so that I can ensure only the active player can click and I can send individual messages to each player.



We have been looking at using Spring Security, but we have been having issues with this. Identifying clients with users & passwords seems like overkill as we are not concerned about security, is there a better approach? Essentially, what is the best way to manage distinct users and then serve them with individual messages/actions?







javascript java spring reactjs rest






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 14:04









saechedsaeched

12




12













  • Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

    – brk
    Nov 21 '18 at 14:06











  • session cookie?

    – epascarello
    Nov 21 '18 at 14:09











  • @brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

    – saeched
    Nov 21 '18 at 14:09











  • @epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

    – saeched
    Nov 21 '18 at 14:10






  • 1





    @saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

    – brk
    Nov 21 '18 at 14:10





















  • Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

    – brk
    Nov 21 '18 at 14:06











  • session cookie?

    – epascarello
    Nov 21 '18 at 14:09











  • @brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

    – saeched
    Nov 21 '18 at 14:09











  • @epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

    – saeched
    Nov 21 '18 at 14:10






  • 1





    @saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

    – brk
    Nov 21 '18 at 14:10



















Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

– brk
Nov 21 '18 at 14:06





Take the machine ip and create a user session once the user looged in. If the user again want to log in check if previous session is active.if so then decline it

– brk
Nov 21 '18 at 14:06













session cookie?

– epascarello
Nov 21 '18 at 14:09





session cookie?

– epascarello
Nov 21 '18 at 14:09













@brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

– saeched
Nov 21 '18 at 14:09





@brk sure, in sudocode that makes sense, but what's the correct way to implement this in the given frameworks?

– saeched
Nov 21 '18 at 14:09













@epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

– saeched
Nov 21 '18 at 14:10





@epascarello session cookie is what I have seen other people discussing, but how does Spring implement this and send messages to individual sessions?

– saeched
Nov 21 '18 at 14:10




1




1





@saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

– brk
Nov 21 '18 at 14:10







@saeched you want me to write the code for it? I think by now you have the idea, it will be much better for you if you pick each of the step and search how to do that

– brk
Nov 21 '18 at 14:10














1 Answer
1






active

oldest

votes


















0














You'd do it just in the same way that you'd do with VanillaJS i.e. gather as much information as possible from the visitor such as ip address, user agent etc.



Here is a list of available thing you can gather.
https://javascriptsource.com/browser-properties/



You might then base64 encode this information so that it creates a semi unique string. This could then be put in a database from which you'd query unique entrances.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413834%2fidentifying-unique-browsers-with-a-spring-backend-and-react-frontend%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You'd do it just in the same way that you'd do with VanillaJS i.e. gather as much information as possible from the visitor such as ip address, user agent etc.



    Here is a list of available thing you can gather.
    https://javascriptsource.com/browser-properties/



    You might then base64 encode this information so that it creates a semi unique string. This could then be put in a database from which you'd query unique entrances.






    share|improve this answer




























      0














      You'd do it just in the same way that you'd do with VanillaJS i.e. gather as much information as possible from the visitor such as ip address, user agent etc.



      Here is a list of available thing you can gather.
      https://javascriptsource.com/browser-properties/



      You might then base64 encode this information so that it creates a semi unique string. This could then be put in a database from which you'd query unique entrances.






      share|improve this answer


























        0












        0








        0







        You'd do it just in the same way that you'd do with VanillaJS i.e. gather as much information as possible from the visitor such as ip address, user agent etc.



        Here is a list of available thing you can gather.
        https://javascriptsource.com/browser-properties/



        You might then base64 encode this information so that it creates a semi unique string. This could then be put in a database from which you'd query unique entrances.






        share|improve this answer













        You'd do it just in the same way that you'd do with VanillaJS i.e. gather as much information as possible from the visitor such as ip address, user agent etc.



        Here is a list of available thing you can gather.
        https://javascriptsource.com/browser-properties/



        You might then base64 encode this information so that it creates a semi unique string. This could then be put in a database from which you'd query unique entrances.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 15:34









        FotoncitoFotoncito

        357




        357






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53413834%2fidentifying-unique-browsers-with-a-spring-backend-and-react-frontend%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Paul Cézanne

            UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

            Angular material date-picker (MatDatepicker) auto completes the date on focus out