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



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

Integrate Persistent Login Into Existing Login

  • Filter
  • Time
  • Show
Clear All
new posts

  • Integrate Persistent Login Into Existing Login

    I have an existing Login UX Component that I want to integrate persistent login functionality into. This Login UX Component has an embedded Main UX component (main app). I took the persistent login template and tried to copy what was in it to my existing login component. What I copied was the Xbasic function code, Server-side event called "canAjaxCallback", and Client-side event called "onRenderComplete". I guess it isnt as easy as just copying this code into my existing login component! When I login, a message saids, "Login has expired, please login again" however it does login and I can see my Main Application. However, within my main application, a couple of List Controls are not filtering correctly, I assume because the session variable is not being set correctly now when the user logs in. Also, when I try to logout for persistent login by calling the logout function, nothing really happens. What should happen is when a user logs out, they should go back to the main login UX component, to the login panel card. Any ideas of what I need to do to integrate persistent login into an existing login component?

  • #2
    Re: Integrate Persistent Login Into Existing Login

    Hi Steven,

    I am also working on getting the persistent login template to work with an embedded component. I think I have gotten all of it to work except for session variables. Here is what I did (also see the attached xara picture that I made to try and understand what's going on):

    I did the reverse of what you did: I replaced my login component with the persistent template and then moved stuff from my old login component back to the new one (mostly the layout and something I had in one of the events).

    It is important that "Has integrated login functionality" is unchecked.

    I embedded my application UX and checked "Delay render is visible". Without this one gets an infinite loop. I set the security for the embedded UX to "always allowed". Otherwise, there are cases where one gets an infinite loop. (If the token is still good but the session has timed out, the onRenderComplete event redirects to the application panel which causes the embedded application component to be loaded, which causes a redirect to the login page, which causes the onRenderComplete event to fire -> infinite loop.)

    I moved the xbLogout callback function into the embedded component where my logout button lives and adjusted it:

    function xbLogout as c (e as p)
    'log the user out of the Alpha Anywhere security framework	
    dim jsOut as c 
    'Create the Javascript response to send to the client. The Javascript must:
    'return focus to the login panel
    'delete the token from localStorage
    'delete the token from the UX state object so that it does not get sent to server on subsequent Ajax callbacks
    'SBG: xbLogout is called from the embedded UX sw_medium and not from the login UX as in the persistent 
    'login example component. I therefore had to adjust the code to use a pointer to the parent UX:
    'Here is the original code:
    'jsOut = "{dialog.object}.panelSetActive('PANEL_LOGIN');" + crlf()+\
    '"var key = '" + e.tmpl.guid + "';" + crlf()+\
    '"localStorage.setItem(key,''); " + crlf()+\
    '"delete {dialog.object}.stateInfo['token'];" 
    'xbLogout = jsOut
    'And here is the adjusted code:
    jsOut = "var p_loginux = {dialog.Object}.getParentObject();" + crlf()+\
    "p_loginux.panelSetActive('PANEL_LOGIN');" + crlf()+\
    "var key = p_loginux.componentGUID;" + crlf()+\
    "localStorage.setItem(key,''); " + crlf()+\
    "delete p_loginux.stateInfo['token'];" 
    xbLogout = jsOut
    end function
    I copied the code in the login component
    Attached Files