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

App Security and MD5 encryption

  • Filter
  • Time
  • Show
Clear All
new posts

  • App Security and MD5 encryption

    I have a mobile app with a remote connection the a WordPress database. I need to validate that the password entered into the security of the app (using Alpha's Security Framework) matches the hashed password on the back end. I want to use Alpha's security so that I can develop using the security tools that are built in, plus I don't have to make a bunch of API calls to the remote server. The goal is to get the MD5 hash to be the same on both systems. Ideas?

    I have admin connection to the remote database and it works fine. The only issue is validating the password that is already stored, and when creating a new user from the mobile app that it creates the password the same way as WordPress. So....I know there is a php script called phpass.php and I'd like to basically duplicate what it's doing. Or maybe even run that on the Alpha server (with IIS and PHP turned on).

    Anyone have any concrete ideas on this?

  • #2
    Re: App Security and MD5 encryption

    Not any ideas but php md5 function and alphas md5 function operate exactly same way.


    • #3
      Re: App Security and MD5 encryption

      Hey kkfin,

      Thanks for the reply. The issue is that WordPress uses an 8 pass iteration after a salt has been applied. So, I'm not sure of how to get the original salt that was added so that it can even go through the first iteration much less 8 passes. Somehow I need to know the salt value that was originally used, and if a new users is created in the mobile app it has to create a salt and store it as well, or WordPress won't know how to validate it. This is the issues as I've determined so far. Hopefully that clarifies things a bit.


      • #4
        Re: App Security and MD5 encryption

        Do not know anything about WordPress but why not handle in your mobile app the login procedure with WordPress and if success then redirect to Alpha backend and do whatever is needed?


        • #5
          Re: App Security and MD5 encryption

          I would like to use the security functionality WITHIN Alpha due to what it allows you to do within the application. There are many benefits to using the security framework. Plus, supposedly it can work, as here is a quote from Alpha about it...
          "And Alpha’s Integrated Authentication can be used with LDAP, OAuth, and Microsoft’s Active Directory, allowing for single sign on...."

          If I can configure my WordPress site as an OAuth Server (which I have installed and it is) then I should be able to use Alpha Security to connect.


          • #6
            Re: App Security and MD5 encryption

            The whole idea behind LDAP, Active Directory and from what I can tell OAuth, is the application seeking authentication doesn't know the password and need not know the password. That authentication provider keeps track of the password. The application seeking authentication knows the password as far as may gather it from the user and pass it to the authentication service, but that is it. So if Alpha5 supports OAuth it should not need to know or keep track of the password for any users That is the purpose of this OAuth etc.
            At least that is the may understanding of this stuff, I hope it helps.


            • #7
              Re: App Security and MD5 encryption

              Hey Paul,

              You are right, and that is the question: Getting Alpha to work with says it can but I can't find ANYTHING that demonstrates it (other than a Twitter feed thing, but it's depended on built in Twitter functions from what I can tell).


              • #8
                Re: App Security and MD5 encryption

                Let me recap what the needs are:

                My client has a web based application in WordPress which has a user registration system. I need to develop a mobile application that can login existing users and create new users. If they register on the mobile application it must also create an account on the web application. So, it seems to me that there would be a way to leverage Alpha's secondary login capabilities to make this work. Given that WordPress is used on 30% if the worlds sites it would seem a natural fit to make this work. I really was assuming that someone had cracked this cookie before.

                I have mentioned md5, oauth, and all that because I'm not sure of the path to take. If anyone has any ideas, even if very different from my own, I'd love to hear them.