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

A5ws_GetCurrentUser() and Session Time Out Behavior

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

    A5ws_GetCurrentUser() and Session Time Out Behavior

    Wonder if one of the guru's could help me clarify something regarding session timeout and the current user id.

    In my system, I check to see if the session has expired by using the following code:

    if .NOT. eval_valid("session.xyz") then
    fnRefreshSession()
    end if

    On each page/dialog, I do this check first. If the primary session variable is not active then I call the "fnRefreshSession()" that re-loads the session variables from the database.

    That works fine....

    My question is how to determine the current logged in user. My current method (v11 and before) uses the ULINK session variable. Here is how I get the info:

    currentuser = session.__protected__ulink

    Now my understanding that ulink is frowned upon/going away due to IIS integration. And you should use the "A5ws_GetCurrentUser" function instead. So I placed the following line in my code.

    currentuser = A5ws_GetCurrentUser()

    Now if I call that line when the session is still valid, I get the correct user id back.

    But....if I call that line after the session has expired, I get a null value.

    I thought (and it could be a wrong assumption) is that the A5ws_GetCurrentUser() works both when the session is valid and when it has expired.

    If that is incorrect, and I am not supposed to use the ulink capability, how can I determine the user id of the current user after session time out?

    Thanks in advance.

    #2
    Re: A5ws_GetCurrentUser() and Session Time Out Behavior

    The user is logged in for the period listed in the Security Settings for login expiration. The default (and suggested) policy is to expire the login when the session expires. When the user login has expired, a5ws_GetCurrentUser() will return a blank value as no one is logged in.

    Comment


      #3
      Re: A5ws_GetCurrentUser() and Session Time Out Behavior

      Originally posted by JerryBrightbill View Post
      The user is logged in for the period listed in the Security Settings for login expiration. The default (and suggested) policy is to expire the login when the session expires. When the user login has expired, a5ws_GetCurrentUser() will return a blank value as no one is logged in.
      Thanks for the fast response. I actually have the "Login Expiration Policy" set to "Expires when the user closes their browser". I am enclosing a screen shot of the current security settings.
      5-11-2013 10-05-58 PM.jpg

      Comment


        #4
        Re: A5ws_GetCurrentUser() and Session Time Out Behavior

        They was a bug in that process in some early V12 builds. If you are using the latest V12 build, that should be working and the user should be found. However, that process relies on a tracking cookie on the client computer, so if cookies are off on that browser, the expiration policy will always be by session

        Comment


          #5
          Re: A5ws_GetCurrentUser() and Session Time Out Behavior

          Thanks for the clarification. I am going to update my solution based upon your input!

          Comment

          Working...
          X