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

Lockout user while connected to Active Directory

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

    Lockout user while connected to Active Directory

    I am successfully using the Active Directory authentication on my site but am concerned about one major issue. The site is mainly used internally but is available for employees that travel through our website. Since it's open to the web, I'm afraid that if a malicious attempt to access the site it may lock down our Active Directory after too many failed attempts.

    When not using AD as the login source, it's possible to set a maximum attempt value so the user is locked out for a period of time. Is there any way to still enforce this rule while using AD so that Alpha locks the user but AD does not?

    Any help would be appreciated.

    #2
    Re: Lockout user while connected to Active Directory

    Normally you set this at the AD domain level
    http://www.omnisecu.com/windows-2003...out-policy.php explains howto

    If that is not working for for some reason create a table for websecurity users with a field lock yes/no. I have no clue how AA implements the AD user policy not tested yet.

    Comment


      #3
      Re: Lockout user while connected to Active Directory

      Thanks for the reply bea. I know how to set up AD to handle user's login attempts and I really don't want to have to handle to users table inside Alpha because the data would not stay live with AD (in case someone changes their password or a new user is added).

      I see that currently Alpha is set up to allow AD to handle all aspects of the login, which is great normally, but I would Alpha to block a session after too many failed login attempts while still connected to AD (not allowing AD to shutdown a windows user even though they are locked out of Alpha). How would I go about requesting this be added?

      Comment


        #4
        Re: Lockout user while connected to Active Directory

        If you look at the security setting there is a field for lockout after x attempts of login failure you have to test this against AD, i think this setting is standalone and the results failures are logged in the log file or you can write a simple UDF in replacement.
        BTW are we talking about inter or intra net users?

        Comment


          #5
          Re: Lockout user while connected to Active Directory

          The setting that allows you to choose lockout options is no longer available once you enable security via AD. Most users will be intranet but the reason I want this change is so those same users can access via internet. If I open to the internet with current AD settings, a simple brute force attack could lock out every user in the company.

          Comment


            #6
            Re: Lockout user while connected to Active Directory

            Create two instances one external ip the other on the local netwerk you can filter the ip where is comming from in the was setting [ bound to ip] the rest is pending on you hardware infrastructure

            Comment


              #7
              Re: Lockout user while connected to Active Directory

              Originally posted by bea2701 View Post
              Create two instances one external ip the other on the local netwerk you can filter the ip where is comming from in the was setting [ bound to ip] the rest is pending on you hardware infrastructure
              create two instances? Do you mean 2 separate application servers? Also, if I am filtering dedicated IP's, wouldn't that mean my users would always have to access from a static IP address?

              Thanks for your help.

              Comment


                #8
                Re: Lockout user while connected to Active Directory

                If you have one was lic upto 4 cores on one machine is what u can run. Configure 1 instance for internal use for NAT with AD behind the firewall the second bound the was instance to an external ip on the machine [outside world].
                You can trace and filter on ip but that is not 100% success and for mobile devices impossible.. Bind the instance to an ip/nic means it will not listen to other traffic works perfect to split your internal and external users. For External use the normal was security settings. Create 2 instances = 2 application servers = yes

                Comment


                  #9
                  Re: Lockout user while connected to Active Directory

                  Does Alpha with the AD integration provide the ability to use AD security groups in Alpha to control access to pages/components/elements?

                  Comment


                    #10
                    Re: Lockout user while connected to Active Directory

                    Originally posted by coleresources View Post
                    Does Alpha with the AD integration provide the ability to use AD security groups in Alpha to control access to pages/components/elements?
                    Yes. You can import your current AD user groups once you've connected to the server. Then you have the option to allow access via the normal security groups options in components.

                    Comment

                    Working...
                    X