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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Persistent login (e.g. users logs in for two weeks)

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Persistent login (e.g. users logs in for two weeks)

    Mo,

    You might want to clarify specifically what your situation is. The answer varies accordingly.

    Specifically:
    • Only desktop users?
    • Only browser users?
    • Only mobile users via PhoneGap-wrapped apps?
    • Some combination of the above?


    If you have a desktop app (old-style Alpha constructions) then I can't speak to it as I'm only
    in the browser/mobile space. I would imagine you could simply set your security considerations
    to allow continuous login for a specified period (as you can with mobile/browser).

    If you are using security managed by a webserver (true for both browser-based and mobile-based apps)
    then you can do this:
    • open your project
    • open the web-projects window
    • at the top, choose the option "Web Security", which will open a window
    • then choose the "Web Security Configuration"
    • you will get another window... this one with several TABS at the top
    • choose the "Login Options" tab and adjust the "login expiration policy" and the "login expiration time"
    • see the example below


    The challenge
    • The normal method for login control is accomplished through "session variables"
    • If the server bounces or the session dies, your login information and any variables you maintain to manage the login process will vanish
    • the noted example (earlier in this post) is outside of session variables and works with a cookie on the browser
    • which means... it works great for cases (e.g. desktop) or mobile (browser access, not PhoneGap) where cookies are enabled
    • but... this method DOES NOT WORK for PHONEGAP apps because phonegap does not enable cookies for its execution of components.


    The ultimate solution
    • as of today (Oct 30th, 2014) there is not a good solution for Alpha-centric persistent login from a PhoneGap app
    • you can't use stored (offline) LISTS or variables to store the login or password because they would still be accessible to a reasonable hacker
    • you CAN achieve a similar effect by storing logins/passwords in a standard table and then encrypting and decrypting the password on the server side (only passing an encrypted version back to the Phonegap app)
    • however... this question has come up enough that some efforts are currently underway at Alpha to address it with a built-in solution.
    • Note: that information comes from another user here on the forum who (along with myself) are directly affected by mobile-centric persistent logins.
    • Finally... if your app is consumer-centric (not corporate in nature) then you can engage the built-in Facebook and Google+ (or other social media) options introduced in September 2014.


    Whether we have useful code or techniques to share depends on whether you are using A5W pages, UX components accessed from a browser, or UX components in a PhoneGap app.

    Comment

      #17
      Re: Persistent login (e.g. users logs in for two weeks)

      Parkjammer,

      Thanks for heaps of information you published here,
      My issue is about "Only browser user" and I have tried that solution you have recommended. but still I have problem when I close the browser and open it and want to go to the web site it still ask me about the username and passwords, that is my problem . I want to keep log in even I close the browser.

      You recommendation works properly for the closing the a tab of a browser . if the browser is still up (even with no page) after try to go to the web site it log in automatically without any problem.
      Could you help me to find it out is it my bad to how I reconfigured the application or is there any other way to close the browser and open it and log in automatically like many websites like Facebook or yahoo and etc.

      Comment

        #18
        Re: Persistent login (e.g. users logs in for two weeks)

        I have a set of mobile components (UX components) that I can
        access either via browser or via PhoneGap apps.

        My settings are those that I noted in my prior post. I have set
        my "expiry time" to "1 day" at present (may be two weeks later on).

        I open a browser, log-in, and then kill the browser (all open browser
        sessions are killed... nothing is left running).

        When I launch a new browser I remain logged in when I hit the
        same site (an A5W page that launches a UX).

        If you have set the expiry method and the expiry time as I noted
        prior, then the other thing you may want to do is clear your browser
        cache (including downloaded apps and cookies) and the completely
        exit your browser.

        Then try it again.

        I haven't done more than this and it has worked for me.

        (Allan)

        Comment

          #19
          Re: Persistent login (e.g. users logs in for two weeks)

          I posted my auto-login code here: http://msgboard.alphasoftware.com/al...371#post682371

          I know it works because it has been running fine since I first sent it to Allan. I later tweaked it to only auto-login from my office IP address.
          Steve Wood
          See my profile on IADN

          Comment

            #20
            Re: Persistent login (e.g. users logs in for two weeks)

            Originally posted by Steve Wood View Post
            I posted my auto-login code here: http://msgboard.alphasoftware.com/al...371#post682371

            I know it works because it has been running fine since I first sent it to Allan. I later tweaked it to only auto-login from my office IP address.

            Steve can correct me if I am wrong, but I believe Steve's code is designed for situations where you are using A5W pages (for example, an Alpha-based website).

            In my case, I'm using a single and completely empty A5W page to launch the initial UX component and then all other actions are UX components.

            Therefore, the only thing I needed to do was ensure the web security settings are set up as noted in my prior posts.

            Certainly, if you are in a pure A5W environment, Steve's is the better and more controlled method.

            Allan

            Comment

            Previous 1 2 template Next
            Working...
            X