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

Help with UX Login component

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

    Help with UX Login component

    Can someone help me to get this very small and simple login component to work...?

    In the attached project, I have the index.a5w containing a UX with "integrated login functionality", and I have the login.a5w page with a classic login component.

    The classic login component works fine, but the UX based login continue to fire the "afterfailedlogin"-client-side-event.

    I have one user account defined:

    Username: [email protected]
    Password: Password

    The project is built as simple and plain as I could possibly do. I think I have now starred myself blind on this for a whole day, without getting anywhere. I think the problems is caused by a small and simple thing I haven't yet done.

    Helping to solve this problem will be highly appreciated. And hopefully, I can afterwards continue to also make "alternative login" work.

    Thanks in advance.
    Attached Files

    #2
    Re: Help with UX Login component

    There's lot of stuff going on here... and I'm not sure if you really mean to include it all.... maybe so... and you're just testing difference scenarios. It can all get a bit confusing because there are a number of very similar avenues to take regarding security... and Alpha doesn't always make it clear how it all should work.

    The main problem you're running into is that the code behind the Login Component and Integrated Component are not as matched as they should be... or maybe there's a bug in one of them. The Login Component will allow a password of "Password". The Integrated Login will not. Change your password to 11111111 (or actually anything else probably) and both will work.

    Just want to check... you know that the Login Component and Integrated Login are 2 different login tools... right? WebSecurity configuration is tied entirely to the Login Component... and just a bit to Integrated Login. E.g. the Redirect page - login is used in the Login Component... but not used in Integrated Login. Integrated Login and purely standalone. You use .login() and .logout() to get in and out of security, but after that you look after everything else.

    Comment


      #3
      Re: Help with UX Login component

      Thanks so much David... Yes, that was it: Changing the password solved the problem - I could have been fighting this problem for days... :-)

      ... I did think, that the Login component (I called it classic login) and the Integrated Login were two ways of doing the same: Ie. create a session state on the server that the a user was authenticated correctly and logged in. So I did think, that irrespective of which method was used to login, if a component or a page was protected with security (page security or component security), a user would be granted access if he/she was member of the necessary groups.

      I did think that the automatic redirect after login was only working (or relevant) for the (classic) Login component, and that this was the primary difference.

      Can you elaborate on how they are different, and what to be aware of when using these different methods ?

      I will continue now and look on "Alternative login" using Google, Microsoft, Facebook etc... I have noticed that it appears that this is only supported for UX components through Action scripting. But again I will expect, that if a user has been authenticated using an alternative login provider, this will grant access also to A5W pages protected with permissions, when the user account is member of the necessary groups. Or are there more twists to this also ?

      Thanks...

      Comment


        #4
        Re: Help with UX Login component

        You can use either login process for web, but only integrated for mobile. When I say mobile, I mean mobile... installed... as opposed to running a web page on a device.

        The Alternative login stuff is a straight forward as it can be... and your premise is correct.

        Comment


          #5
          Re: Help with UX Login component

          Yes, that makes sense regarding "mobile".

          I am making progress again, and I am happy.

          Thanks :-)

          Comment


            #6
            Re: Help with UX Login component

            I got the following feedback from Alpha support:

            This is actually not a bug, but an unusual condition that should not occur in a published application. You have the password field set to use a watermark and the text of the watermark is exactly the same as the password you are entering. When the data is submitted, if the text in the field is still the watermark text, the code removes the watermark and sends a blank value. Since the password data sent to the login was blank, the login fails.

            You can verify this by removing the watermark, use text for the watermark that can never be a valid password (like "Enter Password"), and change the user password to some other value, even a lower case "password".

            In a production system, it would be highly unlikely (and not recommended) to use a password named "Password"
            This makes sense, and I think it is a fine solution, that will most likely not be a problem in all real world scenarios...

            Comment


              #7
              Re: Help with UX Login component

              Makes sense... but should still be handled by Alpha processing... unlikely as it may be.

              Comment

              Working...
              X