Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Unique user ID

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unique user ID

    Hello,
    I have a web application with the security framework on. It all works fine but I would like to ensure that only 1 (one) user can login using its user name and password.

    At present more than one user can login using the same user name and password. Can anyone help?

    I went through the A5 documentation but I could not find anything related to this.
    Thanks in advanced.
    Javier

    #2
    Re: Unique user ID

    What you are asking here is to limit a user to have only 1 session active per user.

    What you could do upon login is save the user's ID in a table if it does not already exist.

    It may be tricky though because users may simply close their browser & then you cannot execute some script to delete the entry in the table. You'd have to think on how you would cope with that.
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


      #3
      Re: Unique user ID

      Is it a problem of people sharing their login accounts, so that more than the person originally authorized is getting in?
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: Unique user ID

        Steve,

        I think you are right if I reread Javier's question. In that case 2-factor authentication would be a solution. If we'd have an easy way to integrate Google single sign on into the Alpha security system then that would be great.
        Frank

        Tell me and I'll forget; show me and I may remember; involve me and I'll understand

        Comment


          #5
          Re: Unique user ID

          Thanks guys. Yes Steve, it is a problem of people sharing their logins accounts so that more than the person originally authorized is getting in
          Javier

          Comment


            #6
            Re: Unique user ID

            Would it be of any use to track the workstation's mac address and only allow login from a certain number addresses? However, getting at the mac address takes an active-x control or something external to Javascript. It can be difficult to retrieve:

            http://stackoverflow.com/questions/3...-in-javascript

            There is the variable, "request.Remote_Addr", which returns an ip address, but it is the same value for workstations behind a common firewall.

            Comment


              #7
              Re: Unique user ID

              Rich,

              That would bind the legitimate user to a particular PC. I think 2-factor is the only way to go; you could send them an email as the 2nd factor upon each login attempt with some code they have to enter to finally login.
              Frank

              Tell me and I'll forget; show me and I may remember; involve me and I'll understand

              Comment


                #8
                Re: Unique user ID

                Frank,
                I was thinking of maintaining a list of approved mac addresses for a particular login ID. That way a user could use multiple computers. For each new mac address a confirmation/activation email would be sent out to the user for 2nd level/factor validation, like you suggested. Although, I don't think using a mac addresses is going to address the original question for the case where two users share the same computer. In that case, the app would probably need to be coded specific to the OS. Under Windows the app would have to get the Windows User ID. If running under a guest or generic OS user ID then there is not much one can do.

                Comment


                  #9
                  Re: Unique user ID

                  My bank account does similar. If I login from a "previously unknown computer", it requires me to go through a few hoops to connect to my account. They use a 3rd party plug in that sends me an authorization code in a text message to my mobile. I have to enter that code to connect. I know it uses cookies rather than machine name to identify the computer because I routinely purge all of my cookies and it then asks me to re-confirm.

                  In your case a little legal language might help as well -- something like a $10,000 fine for knowingly sharing their login with someone else, and mention that you "keep track of such activity" and how you aggressively file suit against any violators. This would go in your Terms and Conditions. You can keep track of all logins right on the login.a5w page with something like this (SQL example):

                  <%a5
                  'saves login to LastLogin on User Mgmt
                  if eval_valid("submitbutton")
                  if eval_valid("userid")
                  dim cn as SQL::Connection
                  dim args as sql::arguments
                  cn.open("::name::conn")
                  vsql = "INSERT INTO web_stats (userid,lastlogin,ipaddress) VALUES (:userid,:lastlogin,:ipaddress)"
                  args.add("userid",userid)
                  args.add("lastlogin",now())
                  args.add("ipaddress",request.remote_addr)
                  cn.Execute(vsql,args)
                  cn.close()
                  end if
                  end if
                  %>
                  If you put this on the login.a5w dialog, the userid will contain their login username.

                  That code is from memory so might need some tweaking (but probably not) and error trapping (a little).
                  Steve Wood
                  See my profile on IADN

                  Comment

                  Working...
                  X