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

Login Component Mobile App

  • Filter
  • Time
  • Show
Clear All
new posts

    Login Component Mobile App

    V12. Build 5667

    I am having a problem with the Alpha template called SecurityFramework-LoginComponentMobileApp

    As per the instructions I have embedded my UX component in the PANEL_APPLICATION card and ticked Delay render till visible and Refresh when panel card gets focus.
    The embedded UX has security set to Requires Login

    When I publish locally and run in a browser I can login but as soon as the PANEL_APPLICATION card gets the focus it navigates back to the login page. Because I am already logged in it then just gets stuck in a continuous loop, navigating to the app, then back to the login page and around and around until I kill the page.

    It is as if the UX component I have embedded doesn't recognise that the user is logged in. I am definitely logging in with a user that has rights to access the embedded UX.

    I saw a post that suggested setting the embedded UX security to always allowed but I don't think that should be necessary.

    All help appreciated.

    Re: Login Component Mobile App

    Hi Richard,

    I've been frustrated by user login, but I believe the login page needs to be
    always allowed so that if someone is not logged in , they can enter their credentials.
    Once they successfully login, they should be directed to an after-login page that
    is restricted by Requires Login.
    Gregg is a great site to test and share sql code


      Re: Login Component Mobile App

      Thanks Gregg but my login page is set to always allowed. Logging in isn't the issue, bringing the embedded UX into view is the issue as described above.


        Re: Login Component Mobile App

        What is the action after a successful login ?
        Gregg is a great site to test and share sql code


          Re: Login Component Mobile App

          The UX being embedded must be set to always allowed... or... the Embedded Object must be set to "Delay render til visible" AND all groups must be checked in Requires Login - which is essentially Always Allowed.

          The issue is that the embedded UX, if Requires Login, is loading when the parent UX is loading... and so the child needs security... but... you haven't logged in yet.

          It gets very messy trying to use "classic" Alpha Web Security with a UX Integrated Security... the two were not built to work together.

          With Integrated Security, the model is that everything is set to Always Allowed, and you control who gets to go where after login.


            Re: Login Component Mobile App

            Thanks but as per the original post the looping issue only starts after login, when the embedded UX is brought into focus. The "login" UX loads fine and delay render is ticked for the embedded UX. The logged in user definitely has access to view the embedded UX. I'm at a loss to explain this one but will keep at it.


              Re: Login Component Mobile App

              So the problem turned out to be between the chair and the keyboard Somewhere along the way the user I was logging in with was removed from all groups so didn't have the necessary privileges to load the embedded ux and the ux was doing exactly as it should, returning to the login page but because already logged in the looping began. Threw me for a loop that's for sure!

              I appreciate everyones efforts.