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

Multi-Page Login with Session Variables - sample attached

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

  • Multi-Page Login with Session Variables - sample attached

    So, I found out a few things about session variables and the multi-page login process that I use:

    1. Sometimes Alpha WAS, and Alpha IIS, tell the browser to do a "GET" on the"Redirect page - login" that has been configured in the project's "Web Security / Security Policy" tab, even though at that time there is no reason to redirect the user, because at that point they are already logged on! When the server subsequently receives that bad redirected "GET" it executes the xbasic in the page, but ends up not sending the response for that page. Maybe it sends another page (the correct page) instead. If you have a secured application where users must have the exact link to your login page then you are in for some trouble. In this case the "Redirect page - login" is not going to be configured as the login page; you don't want to make that page public in this scenario. The only people that should be coming into your site will be using the exact URL to your login page. Your "Redirect page - login" is instead going to be a page that tells them "accessed denied" or some such thing. If you like keeping things tidy, you might also want to blow away any session variables if the user is directed to that page, as you don't really know when Alpha might direct someone to this page. And here lies the problem, session variables that you have setup from previous steps in the login process will be blown away when they should not be, if you are being tidy. So, the suggestion here is to not clear or delete any session variables in the "Redirect page - login", under this scenario.

    2. It is possible the random login failure that I observe in the production copy of my application is due to #1 above, or, more likely, it is due to a timing / synchronization issue. In the production app, session variables are stored in a SQL server database on a separate server than the web server. As mentioned by someone else on these forums, there may always be a timing issue that session variables may not be ready to read after they have been written.

    3. I have mentioned this before, but I will repeat it here: Allowing a user to have multiple tabs or instances of a browser open into your application can be extremely dangerous to the integrity of the database if session variables have anything to do with updateable data fields. Session variables are not unique to the browser's tab or instance:
    https://stackoverflow.com/questions/...ch-browser-tab


    Despite its name, the attached project is for regular Alpha WAS, not IIS. I setup this project to demonstrate why a developer might need a multi-page login process. It starts by using the old Login Component, which if you are following some newer recommendations, you should just abandon along with the multiple a5w pages and go with a UX.

    I probably tested the attached program 50 times over a couple of days before it failed as described in issue # 1, above.
    Attached Files
Working...
X