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

Arguments: Are they secure?

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

    Arguments: Are they secure?

    We are in the process of converting our application from using session variables to arguments.

    Are arguments safe?

    Can someone change the value on an argument in the browser that would then give the access to another user's date in a tenant database?

    Thanks.

    #2
    Re: Arguments: Are they secure?

    What kind of connection string are you going to use?

    Comment


      #3
      Re: Arguments: Are they secure?

      This has been my concern as well: Arguments passed into a Grid or UX are always placed in the data sent to the client browser.

      For me though, my tenant variable is a GUID, so I'm not too worried because 1) they'd have to be pretty darn lucky to guess someone else's GUID and 2) values that never change after a person has logged in will remain coded as session variables in my system. So, the tenant variable will remain as a session var. Now I just have to make sure I have never "published" this variable and that everything works without it being published!

      The final kink to my session variable problem, though, is that I have a multi-step login process. It takes more than just a User ID and Password to get into my application. The user must also pick a "data set" and a type of user they want to login as. Each of which are based on the value chosen from previous window. Since I started this project with the original Alpha Login component, I had to implement these as separate a5w pages. The server sometimes does not make the session variables available to the subsequent pages quick enough. Today a user had to try the login process six times before the server was able to keep up with them, as a session variable wasn't ready to be read by the time the server was loading the next page. So, I need to rewrite the login process to use a single UX. Although, in the end I still might end up with the same problem that the session variables are not ready by the time the user gets to the main menu of the application and selects to open a component.

      Comment


        #4
        Re: Arguments: Are they secure?

        I wonder what are the benefits of using UX component for login. It is at least 1500 lines of code plus all javascript.

        Login is very simple task. You get logged or not. Basic login is about 10 lines of xbasic + html form.

        Ken

        Comment


          #5
          Re: Arguments: Are they secure?

          At the point of login, you can do many things.
          You can record failed login attempts and the ip address, not to mention the site were
          at before they came to your site.
          After a successful login, you can set session variables that control the users access
          to information on your site, how you address the user, even how you display your
          info (I have a working example of changing company info including name,logo,
          phone number and email addresses based on the page a user successfully logs in from).
          Gregg
          https://paiza.io is a great site to test and share sql code

          Comment


            #6
            Re: Arguments: Are they secure?

            I was going to try to give my view as to why arguments are much more secure but then found the following that explains it much better than I could have:
            http://www.lavamunky.com/2011/11/why...-stop-sql.html

            Comment


              #7
              Re: Arguments: Are they secure?

              I assume this thread is about single database and many tenants. When you use Alphas multi-tenant driver it uses session variable to initialize TenantID. Using TenantID is then automatically done by connection string. So always right data at right time.

              Comment


                #8
                Re: Arguments: Are they secure?

                Ah yes, I did indeed ignore the multitenant point.

                As for the benefits of using these "heavy" UX components for logins, you may want to load a bunch of shared resources (ie. javascript, css, image files) while the login form has been presented to the user and the user is entering their credentials. Then the after login events, the client device will benefit from already having cached the static resources to give the impression of a much faster website/app.

                Comment

                Working...
                X