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

Which SecuritySettings file is the culprit for breaking security on production server?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Which SecuritySettings file is the culprit for breaking security on production server?

    I see the following SecuritySettings files on the production server:
    It seems that one or more of these cannot be copied from my development workstation to the production server.

    Do any of the above tables get set up one time upon initial setup and then from then on left as is? Or, do all four tables need to be updated at the same time? If they have to be updated at same time then why has my production server decided all logins are now invalid after replacing those files with a new set?

  • #2
    Re: Which SecuritySettings file is the culprit for breaking security on production server?

    By production system do you mean your Alpha project files (which would not have the guid file) or a published copy to localhost (or other local destination)?

    And when you say logins are invalid, does it say the password is not correct or does it let them log in but then say they are not authorized to access a page or similar?

    Typically you can copy all files from a locally published copy up to some other location -- provided that local copy is exactly the same as your target production copy with respect to the page and component security settings, etc. The guid file is the only file not residing in the Alpha project and is generated during publishing time. The one you probably already have in your production copy does not need to be overridden. Another thought, I don't know which file stores the password encryption key, but I am sure if your passwords are encrypted, then you would have to be sure your locally-published copy had the same value for the password encryption as your production environment.
    Steve Wood
    There is no Cloud. It's just someone else's computer.
    Web - Mobile - Hosting - Products - Frameworks - Developer Resources
    AlphaToGo | IADN (100% Alpha Anywhere Websites)


    • #3
      Re: Which SecuritySettings file is the culprit for breaking security on production server?

      Thanks Steve. I was referring to another server that is not at my site. All attempts at logging into the system were receiving the error, "Login Information Incorrect". This was from a "login" component.

      Turns out the problem had nothing to do with the files I mentioned in post # 1. The problem was that the "a5_application.a5i" from my locally published dev system got carried over to a production server.

      For any who cares to answer:
      Wouldn't it be easier to update AA Web App servers if it were possible to deliver a zip file or some kind of install file to the administrator of that server and let he or she run a process that is built into Alpha Web Server to load the web app?