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

Problem with validating security when no password

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

    Problem with validating security when no password

    I have a form that submits new user data to the security system using the built in functions. However, I want to be able to allow users to not enter a password, and I am having trouble setting that up.
    I try this in the on dialog validate event, and it works in debug mode, but not on the actual website:
    Code:
    if e.dataSubmitted.Password <> "" then
    ExecuteServerSideAction("Validate Web Security Values::Validate_Web_Security_Values")
    end if
    Without the if statement, saving the new user in security works fine. But when I use the code above to allow for no password, then when there is a password, the user is not saved at all in the security system. Can anyone help with this?
    Richard Urban

    Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

    #2
    Re: Problem with validating security when no password

    Is the field itself marked as required.
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment


      #3
      Re: Problem with validating security when no password

      Am sure you won't be able to use Alpha's functions for this. Go around the built-in functions and just use sql to update the security tables directly. However, then you also won't be able to use Alpha's built-in Login because it is going to demand a password. (Disclaimer, 99% sure, haven't tested)
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: Problem with validating security when no password

        Actually, it is working now. Maybe there was some lag in the security system updating after I changed the dialog validate code? The field itself is not a required field.
        Richard Urban

        Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

        Comment


          #5
          Re: Problem with validating security when no password

          Security in the Classic server (Alpha server) can be configured to not require a password for login. Security in IIS always requires a password. If a password is required for login, you should get an error if trying to save a new security record and a password was not supplied. You can edit an existing record and not include a password on the Classic server, and can edit all data other than userid on IIS. Changing the userid in IIS requires including a password.

          One possible "workaround" where a password is required is to enter a random password for a new security record, and then just not reveal it. There is a function for the Classic server only that generates a valid random password - "a5ws_RandomPassword".

          Under no circumstances should security tables ever be accessed directly. All access should be through the relevant security functions and methods, such as the Context.Security object which works in both server systems. Security should be considered a "black box" system.

          Comment


            #6
            Re: Problem with validating security when no password

            Originally posted by JerryBrightbill View Post
            ... Under no circumstances should security tables ever be accessed directly. All access should be through the relevant security functions and methods, such as the Context.Security object which works in both server systems. Security should be considered a "black box" system.
            While your statement is understandable for people that may move to IIS, I am wondering if there is something in the works for the non-IIS AlphaAnywhere web server that is going to break all the extra User Login management features we have been able to put into our systems that are not as easily done, or even possible, if we are not able to touch the SQL login tables ourselves?

            Comment


              #7
              Re: Problem with validating security when no password

              Jerry, thanks for the input. The form I use for new customers has a password field, but customers are not required to make a password, so that is the context for my post above.

              For those new to using the web security system, I will offer the following tips:
              When using the edit account for existing user template, the user name and user role can be changed, but not the password. Do not make the guid field editable, or else when you save the record a new (non functioning) security record will be created, instead of making an edit to the existing record.
              When you use the Open a UX to edit current record in grid or enter a new record action scripting action, you can select the rtc variable in the on dialog initialize load web security action script, as long as the username field or userguid field are data bound.
              To change a password, make a separate UX using the change password any user or change password current user template.
              Richard Urban

              Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

              Comment


                #8
                Re: Problem with validating security when no password

                Originally posted by JerryBrightbill View Post
                Security in the Classic server (Alpha server) can be configured to not require a password for login. Security in IIS always requires a password. If a password is required for login, you should get an error if trying to save a new security record and a password was not supplied. You can edit an existing record and not include a password on the Classic server, and can edit all data other than userid on IIS. Changing the userid in IIS requires including a password.

                One possible "workaround" where a password is required is to enter a random password for a new security record, and then just not reveal it. There is a function for the Classic server only that generates a valid random password - "a5ws_RandomPassword".

                Under no circumstances should security tables ever be accessed directly. All access should be through the relevant security functions and methods, such as the Context.Security object which works in both server systems. Security should be considered a "black box" system.
                So how you test these differences? I have impression that AA developer has classic server integrated for testing but if your applications deploy target is IIS server then all testing also has to done in practise using IIS server so you have to have one IIS as a development server also.

                Comment


                  #9
                  Re: Problem with validating security when no password

                  I also had a problem specifying the uuid in my dialog. Rather, I found that I had to let Alpha set the UUID for the security record and then use A5WS_Get_GUID_From_User to retrieve the uuid to save in my own component.
                  Richard Urban

                  Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

                  Comment

                  Working...
                  X