Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 2 of 2
  1. #1
    New to the CF scene
    Join Date
    Jan 2013
    Posts
    8
    Thanks
    0
    Thanked 0 Times in 0 Posts

    What I should send to a JavaScript front end (client) after a user authentication

    I'm sorry, I'm having a mental block: I'm not sure what I should send to a JavaScript front end (client) after a user authentication on the server. I know that there needs to be some controls for the user (user/admin)to click but I'm not sure what to send that's secure and what not to send that's not secure. I've been told hidden controls are not secure. I know how to implement user authentication on the server. I understand a check on the server needs to be made if a control is clicked to check if the user (user/admin) has the right permissions for that control before the server executes the control function (on the server). I know I can set a variable and send it to the front end, once it's received (Ajax response) add controls (appendChild). If I do it this way, I feel it's not secure because all the code to do this is easily viewable by the browser (page source).

  • #2
    Senior Coder
    Join Date
    Jan 2011
    Location
    Missouri
    Posts
    4,719
    Thanks
    25
    Thanked 662 Times in 661 Posts
    This question is not clear. I understand you have just verified a log in. Now where are you send him.her and for what purpose?
    Evolution - The non-random survival of random variants.

    "If you leave hydrogen alone, for long enough, it begins to think about itself."


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •