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

My first A5 web app - users & groups, security

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

    My first A5 web app - users & groups, security

    I've watched Steve Workings' videos on web security - users & groups - and reviewed the docs as well. I'm unclear on how to do something (and unsure it can be done with relative ease).

    As I understand it, there are two primary (and easy) ways to manage user information for login/security purposes. One is through the User & Groups "wizard"; the other appears to be import of pertinent data from an existing table.

    In my app, there exists a USER table. The User table contains loginid, role information, data unique to the user, password, etc. The role field gets used on virtually every page, report, etc.

    It seems to me that the login component should be able to query directly against that table. I'm not able to see how that can be done. It seems, instead, that a recurring import would be required upon the client's administrative personnel making changes. Is that really what must be done? And, if so, how is that best implemented? Each modification by HR would trigger import?

    Please tell me there's any easier way.

    #2
    Re: My first A5 web app - users & groups, security

    how are your HR changing data (or adding new users), through a web app or desk top?

    if web, then if you follow steves guide it shows you how to add a user to security table before adding them to your db table.

    effectively adding the user to the web security before adding to your database.

    the login component queries against the web security tables not your database tables.

    if they are adding users from a desktop app which then needs adding to the web security, well so far im afraid, regular imports to the web security table is the only way i have been able to find and would also like to see a better way to do this.

    Comment


      #3
      Re: My first A5 web app - users & groups, security

      The user information will be modified by HR staff via web page. I don't see how (or why) providing HR access to the Security Table is the way to go. These changes may include critical issues such as ROLE. The ROLE gets used immediately upon the User's successful login and frequently (at every page?) after that.

      Also, as new staff are hired, HR would add the user via the web page.

      As I've continued to search the forum, it seems I'm almost forced to "roll my own" login system. Not an enthusiastic way to begin. ;)

      Comment


        #4
        Re: My first A5 web app - users & groups, security

        you dont need to do your own, the one already in place is good enough.

        to login you only need to create a few fields, username, passowrd, ulink and group.

        these can all be created using the user registration on steves website. then im sure that the user group can be changed later.

        if you havent already seen it have a look at user registration here

        http://www.alphatogo.com/resources.a...lities_Page=2&

        it took me a few times reading through it before it clicked.

        Comment


          #5
          Re: My first A5 web app - users & groups, security

          Jon, that document, which is here, is a little out of date but worthwhile to read. I also have a complete template featured at this location http://wt.alphatogohost.com.
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: My first A5 web app - users & groups, security

            Originally posted by fsi View Post
            Also, as new staff are hired, HR would add the user via the web page.

            As I've continued to search the forum, it seems I'm almost forced to "roll my own" login system.
            What you describe is a very common scenario - one which should be enabled inside Alpha without requiring you to *roll your own*.
            Frank R

            Comment


              #7
              Re: My first A5 web app - users & groups, security

              Describe what you want with a little detail and I will write it.
              Steve Wood
              See my profile on IADN

              Comment


                #8
                Can anyone confirm accuracy of A5 documentation re: security?

                I've been fighting with the Alpha-documented procedure to build a web component that would allow a user (human resources) to add a new user via web page. Honestly, it looks easy enough - and it appears it might do exactly what I need to do. But I can't get it to work.

                http://support.alphasoftware.com/alp...lpv9/index.htm
                Topic Title: "Adding Users with a Web Component"

                In spite of going through the steps some umpteen times, clicking on SUBMIT does not seem to add anything to the web user table as documented. No error is returned, either, although it does return error on validation criteria such as password length, mismatch on confirmation, and conflict with existing userid (where previously entered through A5 IDE Users & Groups).

                This leaves me wondering if there might be a step or two missing from the documentation.

                Can anyone run through the steps (as documented in A5 online help) and confirm?

                Comment


                  #9
                  Can anyone confirm accuracy of A5 documentation re: security?

                  (oops... sorry about the double-post... meant to create a new thread rather than amend my previous thread)

                  I've been fighting with the Alpha-documented procedure to build a web component that would allow a user (human resources) to add a new user via web page. Honestly, it looks easy enough - and it appears it might do exactly what I need to do. But I can't get it to work.

                  http://support.alphasoftware.com/alp...lpv9/index.htm
                  Topic Title: "Adding Users with a Web Component"

                  In spite of going through the steps some umpteen times, clicking on SUBMIT does not seem to add anything to the web user table as documented. No error is returned, either, although it does return error on validation criteria such as password length, mismatch on confirmation, and conflict with existing userid (where previously entered through A5 IDE Users & Groups).

                  This leaves me wondering if there might be a step or two missing from the documentation.

                  Can anyone run through the steps (as documented in A5 online help) and confirm?

                  Comment


                    #10
                    Re: My first A5 web app - users & groups, security

                    I don't have an answer other than to say that documentation must have been recently updated to use some new security functions. The old method used a5ws_save_user_values(CurrentForm,request) whereas the new text shows a5ws_save_webuser_values(CurrentForm).

                    I think part of the problem is not too many have tried the new functions.

                    Can you just attach your dialog for someone to test?
                    Steve Wood
                    See my profile on IADN

                    Comment


                      #11
                      security validation

                      So... did anyone ever come up with a solution to the issue of the login component using a different table? I want the benefits of the security system but need to validate against the client's existing member/name table. Anyone?

                      Thanks!

                      Paul

                      Comment


                        #12
                        Re: My first A5 web app - users & groups, security

                        Steve, where is the new documentation?
                        a5ws_save_webuser_values(CurrentForm)
                        Wisdom is foundational, then add to that knowledge

                        Comment


                          #13
                          Re: My first A5 web app - users & groups, security

                          Its in the normal Help file. Here's how you find it:

                          Type "a5ws_" in the index and pick any of the security functions. Look at the bottom for a link to Web Functions and click that. You get a page of all the functions, except a few unpublished functions. Find the a5ws_save_webuser_values() function and click that.

                          It's not in the Contents, not in the Index, not in the Search.

                          Its also in the Wiki at this location: http://wiki.alphasoftware.com/A5WS_S...webuser_values

                          Here is the web function page if you cant find it.

                          http://support.alphasoftware.com/alp..._Functions.htm
                          Steve Wood
                          See my profile on IADN

                          Comment

                          Working...
                          X