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

IOS Touch ID

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

    IOS Touch ID

    I have been playing with the UX IOS Touch ID template. In testing, it seems to work great. But it almost looks like it is just verifying your fingerprint, and allowing you into the application, not taking into regard any kind of username/password credentials that allows you into the app. So to me it almost seems like it is skipping the step of actually authenticating with a valid username/password. Has anyone implemented this into their apps? Curious what others have done.

    #2
    Re: IOS Touch ID

    Here is the javascript from the touch ID template:

    function initialize() {
    StatusBar.overlaysWebView(false);
    StatusBar.styleDefault();

    setTimeout(function() {
    var pObj = {dialog.object}.getPanelObject();
    pObj.resize();
    },100);


    // enable or disable fingerprint scan button
    var ele = $('{dialog.ComponentName}.V.R1.BUTTON_2');
    window.plugins.touchid.isAvailable(
    function() {console.log('Fingerprint scanner is available.');ele.disabled = false;},
    function() {console.log('Fingerprint scanner is not available.');ele.disabled = true;ele.innerHTML='No Scanner Detected'}
    );
    }

    function verifyIdentity() {
    window.plugins.touchid.verifyFingerprint('Verify your ID',
    function() {
    console.log('ID verified.');
    {dialog.object}.panelSetActive('PANELCARD_2',true);

    },
    function(e) {
    console.log('ID verification failed');
    navigator.notification.alert('ID verification failed: ' + JSON.stringify(e));
    }
    );
    }



    Just seems to me like this is not interacting with any type of login at all, but just verifying a fingerprint and going to a different panel. Anybody know how to make this interact with persistent login?

    Comment


      #3
      Re: IOS Touch ID

      I don't have any experience setting this up but will need to in the next few weeks. Seeing how other apps do it such as banking, I think you need to present the user a login screen where they input userID then the touchID script runs to verify the fingerprint. Essentially touchID is just a faster, more secure password but the magic is put into the app itself when you, the developer, ask a user for permission to use previously setup touchID. I don't know yet how that works.

      Comment


        #4
        Re: IOS Touch ID

        Hi,
        I'm only guessing here but it would seem you might have to do this.

        First have a panel card giving the user the option of using Touch ID and store that in a small encrypted table included with your app. The table would have at least these fields in it:

        touchID, logical
        username, character
        userpassword, character

        Then your app would first check this table to see if touch ID is enabled, if so, then run the javascript shown above with the addition of an ajax callback that would do an auto login using the fields above after the ID is verified or have it call a panel card that would do the auto login.

        Again, that is only a guess.

        Mike
        Mike Reed
        Phoenix, AZ

        Comment


          #5
          Re: IOS Touch ID

          Has anyone tried this anymore to see how to tie the touch id to specific user credentials? So when a user uses the touch id then the user will be logged in and data is filtered based on that specific user?

          Comment


            #6
            Re: IOS Touch ID

            I stopped pursuing this, I never could figure out how to make it work. And I never could find any examples in the forum of anyone that has done it. I'm sure it can be done, but the UX template provided by Alpha is incomplete in my opinion, and doesn't really use touch ID in a practical way.

            Comment


              #7
              Re: IOS Touch ID

              Ok, instead of using Touch ID, can it be set up to let the user remember the username so they don’t have to type that in all the time when they login?

              Comment


                #8
                Re: IOS Touch ID

                Check out the Persistent Login UX Component template in Alpha. It has all of that set up in the template already. It will allow the user to log in once, and then never have to log in again.

                Comment

                Working...
                X