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

Tighten security by having whitelist of machine names

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

  • bea2701
    replied
    Re: Tighten security by having whitelist of machine names

    It's not out the box u have build yourself or send a request to Selwyn, i use it with C# and webapi

    Leave a comment:


  • RichCPT
    replied
    Re: Tighten security by having whitelist of machine names

    Eric, regarding post # 14:
    Yes, I was assuming the use of https. But, to be clear, the two-stage authentication is in addition to using https. Here's Google's description of it:
    https://support.google.com/accounts/answer/185839?hl=en

    Leave a comment:


  • bea2701
    replied
    Re: Tighten security by having whitelist of machine names

    Originally posted by RichCPT View Post
    I think for some applications two-stage authentication is the way to go: 1) User enters valid ID and password and they get redirect to 2nd stage login page, 2a) Server sends short SMS message/code to user's cell phone, 2b) User is given certain amount of time to enter the SMS code and proceed to main application page.
    Always use https url that is the standard these days

    Leave a comment:


  • RichCPT
    replied
    Re: Tighten security by having whitelist of machine names

    I think for some applications two-stage authentication is the way to go: 1) User enters valid ID and password and they get redirect to 2nd stage login page, 2a) Server sends short SMS message/code to user's cell phone, 2b) User is given certain amount of time to enter the SMS code and proceed to main application page.

    Leave a comment:


  • frankbicknell
    replied
    Re: Tighten security by having whitelist of machine names

    If you have thousands of ips it might take a while to do a character match. It would be better to do it at the machine level with ip blocker firewall by beethink. Don't let them get to the login page.

    Leave a comment:


  • kkfin
    replied
    Re: Tighten security by having whitelist of machine names

    Or Context.Request.UserHostAddress or Context.Request.Remote_Addr (standalone)

    Leave a comment:


  • Steve Wood
    replied
    Re: Tighten security by having whitelist of machine names

    ?request.remote_addr

    So, up on your entry page, even before login if you want:

    if request.remote_addr is in the list then
    response.redirect("welcome.a5w")
    else
    response.redirect("sorry_cannot_access.a5w")
    end if

    Leave a comment:


  • gilbertro
    replied
    Re: Tighten security by having whitelist of machine names

    Originally posted by Steve Wood View Post
    Alpha has an Allow IP Address list in its web server configuration, but I would not use it because you would have to constantly stop/start your server to implement. Better to create your own table of IP addresses, and stick some xbasic on the index.a5w page that validated their IP against that list, kicked them to a message.a5w page if not allowed. But still, using IP in this way is going to be work for you when their IP changes. They would have to call you, you would have to update the list, etc. Using an IP range as suggested in this thread is not useful because it is the same as allowing any IP address, assuming the potential sinister user is right in the same city, i.e., same IP range. Alpha's built in security is quite adequate provided you only issue credentials to valid users. ALL data is "quite sensitive" and apps require proper security.
    Thanks Steve. What function/code do I use to determine the Client's IP address ? It is easy enough to determine the server's IP address but I need the IP of the client.

    Leave a comment:


  • bea2701
    replied
    Re: Tighten security by having whitelist of machine names

    store the ip control in a user ip range sql table to check perhaps that might help only effective on a internal netwerk

    Leave a comment:


  • Steve Wood
    replied
    Re: Tighten security by having whitelist of machine names

    Alpha has an Allow IP Address list in its web server configuration, but I would not use it because you would have to constantly stop/start your server to implement. Better to create your own table of IP addresses, and stick some xbasic on the index.a5w page that validated their IP against that list, kicked them to a message.a5w page if not allowed. But still, using IP in this way is going to be work for you when their IP changes. They would have to call you, you would have to update the list, etc. Using an IP range as suggested in this thread is not useful because it is the same as allowing any IP address, assuming the potential sinister user is right in the same city, i.e., same IP range. Alpha's built in security is quite adequate provided you only issue credentials to valid users. ALL data is "quite sensitive" and apps require proper security.
    Attached Files

    Leave a comment:


  • gilbertro
    replied
    Re: Tighten security by having whitelist of machine names

    Originally posted by frankbicknell View Post
    What I do which is not perfect but does add a little level of security is I get the range of IP addresses assigned to the provider that the client uses then allow that ip range which will cover any dynamic ip that they may get assigned.
    Frank, this method is useful as well. I can see that you understand my challenges.

    Leave a comment:


  • gilbertro
    replied
    Re: Tighten security by having whitelist of machine names

    Originally posted by lgrupido View Post
    The entire point of having a webapp is to allow people to access it from anywhere.

    You may also want mobile devices in the mix eventually.

    Do you really want to be responsible for whitelisting every device someone might want to connect to your app with?

    If you really want the app to be computer only and only certain machines, you might be better of with a VPN.
    I am hosting a business web app. The information is quite sensitive and not many clients would be using it. So whitelist would be quite manageable.
    However Larry, your points are valid and useful. I will look into setting up VPN (may need help with that)

    Leave a comment:


  • frankbicknell
    replied
    Re: Tighten security by having whitelist of machine names

    What I do which is not perfect but does add a little level of security is I get the range of IP addresses assigned to the provider that the client uses then allow that ip range which will cover any dynamic ip that they may get assigned.

    Leave a comment:


  • lgrupido
    replied
    Re: Tighten security by having whitelist of machine names

    The entire point of having a webapp is to allow people to access it from anywhere.

    You may also want mobile devices in the mix eventually.

    Do you really want to be responsible for whitelisting every device someone might want to connect to your app with?

    If you really want the app to be computer only and only certain machines, you might be better of with a VPN.

    Leave a comment:


  • Steve Workings
    replied
    Re: Tighten security by having whitelist of machine names

    api_getmachinename() is for desktop applications only. If you do this with a web application it will always return the name of your server.

    Why do you need to use something other than good, standard security -- what problem are you trying to solve?

    Leave a comment:

Working...
X