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

Two factor authentication for A5 (ie PhoneFactor)

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

  • Two factor authentication for A5 (ie PhoneFactor)

    Anyone implemented 2 factor authentication for use with A5? I am looking to secure with PhoneFactor or similar.

    This provides out of band authentication without the need for hardware tokens (uses phone/text message) and is FREE for up to 25 users.

    This would allow remote application users (mobile phones w/o static ip) to access the application and insure identity.

    I assume that with the upcoming IIS integration this would be easy since PhoneFactor support Active Directory but I would rather not use the AD since WAS is on dedicated Windows Server 2008 r2. No other access to this server is needed for users. I am simply trying to secure with 2 factor authentication.

    Brad

  • #2
    Re: Two factor authentication for A5 (ie PhoneFactor)

    I fully support your idea, in fact I have requested it as a feature a few months ago in Alpha's Ideascale so maybe you can vote for it:http://alphasoftware.ideascale.com/a...on/27069-14754

    I think moving to the cloud really needs 2-factor authentication just like Google now offers for it's Gmail service: it gives you the kind of confidence you need to put your stuff out there in the cloud.
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


    • #3
      Re: Two factor authentication for A5 (ie PhoneFactor)

      Frank:

      I just posted on IdeaScale link you provided above. Hopefully we can stir up some more support for this critical step towards making A5 secure with mobile devices.

      Brad

      Comment


      • #4
        Re: Two factor authentication for A5 (ie PhoneFactor)

        Great! I was not aware of PhoneFactor; looks interesting!
        Frank

        Tell me and I'll forget; show me and I may remember; involve me and I'll understand

        Comment


        • #5
          Re: Two factor authentication for A5 (ie PhoneFactor)

          Frank:

          I started looking at PhoneFactor 10 months ago - prior to v11 and recently the large hospital network which my wifes work (doing home health nursing) began using PhoneFactor for ALL users when not connected directly to the local network. This hospital uses Citrix and has digital certs on the individual computers and still found it necessary for the users to use 2 factor authentication. Before using PhoneFactor they were using RSA hardware tokens for the past few years. The other nurses seem to like this new approach and the costs of the tokens and maintenance has been eliminated.

          Brad

          Comment


          • #6
            Re: Two factor authentication for A5 (ie PhoneFactor)

            I just took a look at this - I think that this is going to be important as well... any word on what phonefactor charges for the service? I've GOT to think that it's got some sort of web interface that Alpha would hit on login... This should not be _that_ hard to accomplish.

            Comment


            • #7
              Re: Two factor authentication for A5 (ie PhoneFactor)

              Jeff:

              PhoneFactor is FREE for 25 users or less - no setup / no credit card / no licensing issues etc. I am currently using it to secure the VPS server Remote Desktop since the server is in a datacenter. It has being working very well. It should be noted that you do not provide any information other than user name and phone number - no user passwords outside our own servers. Getting ready to implement RADIUS server to authenticate users to my linux (CentOS) servers in the near future - all for FREE.

              If someone wants to use other 2 factor authentication systems (ie hardware tokens, other phone based systems) the solution I am seeking should work for them as well.

              Brad

              Comment


              • #8
                Re: Two factor authentication for A5 (ie PhoneFactor)

                I get that it's free for 25 users or less. But there's NO such thing as a free lunch! And there's always the odd chance that I may have to go above the magic number of 25. I'd like to know how deep the kim chee is.... NOT asking these kinds of questions has landed me in errr... ummm... _excrement_ before.... so I tend to ask up front!

                (grin)

                Comment


                • #9
                  Re: Two factor authentication for A5 (ie PhoneFactor)

                  Jeff:

                  I understand your cost concern. The vendor I was considering (PhoneFactor) will quote on individual basis - I have not seen any pricing online. The more fundamental concern for A5 is implementation in the security framework of a 2 factor authentication system as an option. This would allow developers to use any number of third party systems or even write their own if desired.

                  My goal is to find an efficient way to implement the authentication whether it be PhoneFactor or something else.

                  Brad

                  Comment


                  • #10
                    Re: Two factor authentication for A5 (ie PhoneFactor)

                    OK - So let me see if I understand this stuff right....

                    Once a user has logged in to the A5 security, there needs to be a second "hook". The login code needs to be able to send out a generic "function call" that will return once the user has been validated via PhoneFactor or [insert service here]. If a positive result is received, then they are authenticated, otherwise they are out o' luck.

                    I haven't yet taken a look at the PhoneFactor SDK, but I can't see this as being too difficult to implement... but I _may_ be missing something...

                    Comment


                    • #11
                      Re: Two factor authentication for A5 (ie PhoneFactor)

                      Actually I think I DO see the problem... I don't see any On_Login type of events that are exposed by the login component in alpha. And that means that the "hooks" aren't available to us. So if we wanted to do this, we'd have to do a new login component from scratch....

                      Any Alpha guys with more experience have any thoughts on this?? Very interesting. Thanks, Brad

                      Comment


                      • #12
                        Re: Two factor authentication for A5 (ie PhoneFactor)

                        Jeff:

                        Your understanding is correct. I have started looking at the PhoneFactor SDK to add java code in A5. I hoping that Alpha would consider adding direct SAML support or similar which would allow developers to choose the authentication provider without hard coding for any specific provider. I am trying to avoid the costs/licensing issues that the calendar module has been plagued with (see other posts to experience the problems first hand). I want a method to plugin the provider of choice with the next result being 2 factor authentication.

                        Brad

                        Comment


                        • #13
                          Re: Two factor authentication for A5 (ie PhoneFactor)

                          Yep - I've seen the calendar festivities first hand. I'll look into it as well. Anybody else that finds this interesting - now's a good time to pipe up!

                          Comment


                          • #14
                            Re: Two factor authentication for A5 (ie PhoneFactor)

                            ... above the magic number of 25. I'd like to know how deep ...
                            On a product roundup page on SC Magazine.com the price for PhoneFactor is listed as $10-$25/user.

                            Comment


                            • #15
                              Re: Two factor authentication for A5 (ie PhoneFactor)

                              Beside phonefactor there are options that are cheaper :



                              1. Build a second login page directly after the primary A5 login and let the user type there PIN# that is not to difficult to build, store the PIN in a employee or user table <encrypted>
                              2. Use a SMS text service API create a random number store it in a session var and send it by the SMS http get service to the user cellphone.
                              What you also can do is to replace the A5 websecurity password with the random number in combination with the A5 sessionID save that somewhere.
                              If the A5 sessionID is not valid then also the random number is false. In this way it saves the user time there is no need for two conformations to login.
                              I think this combination is safe to use and it's a two factor authentication ideal for mobile apps.
                              Some SMS providers offer email2SMS if you think is to difficult to write the http get function then you use the Xbasic function to send a email [plain text].
                              3. If you want to use the mail2sms option be sure to use SHA encryption.

                              Cost:

                              1. your own time
                              2. sms credit cost + your own time
                              3. depending on the provider


                              Eric

                              Comment

                              Working...
                              X