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

User LockOut

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

    User LockOut

    v10.5 Web app

    Using the standard login component, when a user puts in wrong password, on the 4th try they get "Try again later." I have a "Wait time" of 30 minutes.

    Questions:
    [A] If user puts in the correct password on the 5th try, it lets them in, so it does not appear that they are "Locked Out". Any insight on this behaviour would be appreciated.

    [B] If a user is indeed locked out (which should be indicated by using the ?a5ws_get_lockedoutusers('U') function, where is the LockedOut data stored, i.e. a field in some table? I see no such field in the webusers table. Any hints appreciated.

    #2
    Re: User LockOut

    I'm not getting A. It works properly. Are you testing this in localhost? It won't work correctly in live preview.

    B. Good question. Look in the webroot for a file called locks.SecuritySettings
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: User LockOut

      Hi, Peter.

      No, testing this on a dev box which mirrors the production box.

      I suppose we had not really tested this well (no kidding!).

      An incorrect password fails 3 times as expected: "Login information incorrect" is displayed. On the 4th bad password, I get the "Try again later" leading me to assume that the user is now locked out for 30 minutes. However, a 5th try with the correct password lets the user in. Not what I would expect.

      Comment


        #4
        Re: User LockOut

        I misread your post. I get the same thing. She's a bug!
        Last edited by Peter.Greulich; 03-04-2011, 03:40 PM. Reason: Overstated
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment


          #5
          Re: User LockOut

          In post #2 I had tested locking out the user - but not the "logout after failed attempts".
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            Re: User LockOut

            Thanks for your due diligence in testing, etc.

            Also, I have located the Lock file. Doesn`t appear to be much in it. I wonder what the actual functionality is? Does it not check that file if the pword is good? I would think it would check for a lockout before validating the pword.

            Comment


              #7
              Re: User LockOut

              Re: The Locks.SecuritySettings file.
              After forcing a lockout it had this in it.

              xE/dLNUzHdPHeXjlai5qTvdDngOAtVOfSovDwUiWKj8S/umE2HBFCl3uEmN0EKBM

              I am imagining that this is the UserSecID GUID and the time encrypted.

              Comment

              Working...
              X