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

Some users validate and others don't

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

    Some users validate and others don't

    I'm just get into the security part of A5WAS. I can add users, build groups, enable the security framework, set permissions for pages and web components. The development database is local, but the enterprise version of WAS is on a server in our LAN. My webapp finds the data to populate the grids now, but not all of my users will validate. They are all set up identically, being in the same groups, etc. Some will validate in my login page and others won't. This is odd, I thought the users and groups information was in a database. I even rewrite when I publish rather than "publish new or changed". This is goofy. What I am missing here?

    #2
    Re: Some users validate and others don't

    Do any of them not have Javascript or Cookies enabled?

    Comment


      #3
      Re: Some users validate and others don't

      By "validate" do you mean some users can login, while others are rejected when trying to login?

      There are two methods to publish new users to an existing location. (By existing I mean you have published to this location previously.)

      - Click the Publish icon and check Publish Web Security Data Tables. This will re-publish all security information, including Users and Groups.

      - Click Web Security, then Publish Security Files and check Data Tables for Users and Groups. I normally uncheck the Publish New or Modified only box.

      Either of the two above will copy Users and Groups from your development copy to the published location. Note that you would want to avoid this if your web application is designed to add users online.
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: Some users validate and others don't

        I've tried using both methods of security publishing (and I always uncheck the 'publish only new or changed' box also). Cookies or javascript can't be an issue since I am testing all my user logins myself from my own PC. Some work and some don't. I am not adding new users on line. Could the browser be doing some kind of caching or maybe something else?

        Comment


          #5
          Re: Some users validate and others don't

          Originally posted by AAVasaris View Post
          Could the browser be doing some kind of caching or maybe something else?
          Could well be - adding a log-out page always helps make sure... Just add a "Log Out" menu option to your navigation, then create a page called logout.a5w which has the following code at the top and a link to the login page:
          Code:
          <%a5
          A5WS_LogoutUser( Session, Request, Response )
          %>

          Comment


            #6
            Re: Some users validate and others don't

            "Properly" logging out or clearing the page cache will not affect the ability to log in.

            Try this sequence:
            • Modify something in your Users and Groups. Anything, maybe create a brand new user with a simple password.
            • Click Publish, then Clear Publishing History and Yes. Then close that dialog.
            • Go through your same routine for publishing security.
            • Go to your server and look at the location where you published your files for a file named websecurity_users.dbf. See if that file has the current date and time.

            Very often you have to click that Clear Publishing History to cause security files to publish. Alpha's intellegent system to know what files 'need' to be published does not work properly.

            Or, the problem is going to be that you are publishing to a location different than where you think you are, or something like that. If security is properly published, it DOES work correctly.
            Steve Wood
            See my profile on IADN

            Comment


              #7
              Re: Some users validate and others don't

              Problem fixed. I had to delete all of the web security files from the local development webproject and the publishing destination on the server, then recreate the security framework. Every user can log in now. I even tried creating a new user, then publish using the Web Security icon. The change showed up in the development version AND the published version and the new user can log in. A5 must have gotten "too smart" for some reason, and I had to force it to be "dumb" again.

              Comment


                #8
                Re: Some users validate and others don't

                What I proposed would probably have the same effect. All you did was to ensure the local security files published because they were no longer present on the server, prompting Alpha to publish. Clearing the History would have done that.
                Steve Wood
                See my profile on IADN

                Comment

                Working...
                X