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

What happens with login after timeout?

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

    What happens with login after timeout?

    Some of the questions I will be asking will come from situations I have encountered with other tools. I am coming from an environment with a tool that was very powerful, yet it had holes that were, at times, shocking.

    What happens in an Alpha web app when the session times out?
    I imagine if the session times out, it will require another login, yes?
    Does the code generated by Alpha automatically redirect to the login page for another login, or is there just a session timeout error displayed?

    [In this other tool I have been using, the framework takes the time to route the user to another page, but it's an "error accessing data" page, not the login page. N.G. ]
    Frank R

    #2
    Re: What happens with login after timeout?

    Hi Frank,

    You have the ability to set the session length, whether 5 minutes, 8 hours or what ever. When a session does time out and you use Alpha's built in Web Security the user will be directed back to the log on page if they try to view any other page in the web app.

    After logging back in, they will be directed to the previous page they were attempting to visit.
    Dan

    Dan Blank builds Databases
    Skype: danblank

    Comment


      #3
      Re: What happens with login after timeout?

      Originally posted by Dan Blank View Post
      Hi Frank,

      You have the ability to set the session length, whether 5 minutes, 8 hours or what ever. When a session does time out and you use Alpha's built in Web Security the user will be directed back to the log on page if they try to view any other page in the web app.

      After logging back in, they will be directed to the previous page they were attempting to visit.
      Ahh, perfect. :)

      Thank you.
      Frank R

      Comment


        #4
        Re: What happens with login after timeout?

        It's a bit more than that. Session expiration and being logged in are two separate things. There is a configuration setting in Web Configuration where you can set Login to expire when the session expires. Its not the default setting, and unless it is set to do so, when the session expires, you are still logged in, just that your session folder is gone and all session variables that you created are all deleted.

        So, if you have not made the correct provisions for "what if my session expires", your user may get a big fat 500 error if a session variable is needed on page refresh.

        If you have programmed your pages properly, even though the session has expired and the session folder deleted (along with all contents) the user (who is still logged in) will get all of their session variables recreated and repopulated, the browser will create the same session folder and the same session ID, and the user will be unaware that the session ever expired. YOU have to include code in your application that recreates any required session variables on refresh.

        Look at Web Configuration for Web Security. There are several options for determining when the LOGIN expires.

        This is also why I like using the "ULINK" value from Security. It's a special session variable that ALWAYS will be present if the user is logged in, even if the session expired midstream.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: What happens with login after timeout?

          Steve is correct in the user still being logged in after a session expires.

          I on the other hand prefer the user to log back on. It tells me a few things about the lenght of the visit and idle time. In one web app the user name is recorded when a record gets changed or added, so I like to capture that information. I found that some users were leaving the application open all day, sometimes over night. Since they were still logged in and the session expired, the change fields were empty. So I incraesed the session time to 2 hours and then forced them to log back in when the session expired.

          Basically it depends on your client and your users as which approach to take.
          Dan

          Dan Blank builds Databases
          Skype: danblank

          Comment

          Working...
          X