Barcode is invalid, migrations fail about two-factor-authentication HOT 11 CLOSED

@ampodobas thank you for the detailed error message. Can you show me the config file ?

from two-factor-authentication.

@imrealashu:

• I followed the instructions on this page precisely: http://imrealashu.in/code/laravel/two-factor-authentication-in-laravel/.

• When I did a composer require for your project, the version entry was:
  "thecodework/two-factor-authentication": "^0.1.3",

• There also seems to be an issue with the ajax() request conditional. It worked after I amended the controller (in vendor for this project) from if ($request - ajax()) { to if ($request ->ajax()) { in TwoFactorAuthenticationController.php.

from two-factor-authentication.

I'd suggest use version 0.1.2 for now, I'm working on #13 and it is currently in WIP. I'll solve it at the earliest.

from two-factor-authentication.

@imrealashu: many thanks. I've tried a number of other two-factor auth packages for an InfoSec monitoring tool I'm developing using Laravel and none intercepted the authentication request upon a successful login like your's did. I look forward to using it, and I appreciate the quick follow-up.

from two-factor-authentication.

@ampodobas sure, I'll resolve those issues and put an stable update soon. Meanwhile if you spot any error or bug using version 0.1.2 do create an issue, I'll try to resolve it asap.

from two-factor-authentication.

@ampodobas I've fixed the issue and will put an update soon. The actual problem was the migration which further failing generating valid barcode. Thank you for trying it out and creating the issue. Closing it for now, will notify you once I put an update.

from two-factor-authentication.

@ampodobas I've released an update 0.1.4, it tested and can be added in your project. However 0.1.5 version is releasing anytime soon today which adds a new feature to specify your User model and table gives more flexibility to projects where user have multiple authentication.
I look forward to your review and feedback. Thank you.

from two-factor-authentication.

@imrealashu:

(1) The same issue about the invalid barcodes is persisting:

(2) The multiple equals signs (which I've never seen in any secret key before) are still being appended to the typically "normal," alpha-numeric secret key. I think solving how the secret key is generated and inserted should be dealt with first. If you want me to help test anything, I would benefit from it because I want to use this package as quickly as possible in my project.

from two-factor-authentication.

@ampodobas
I don't think that's an issue and I'll explain it to you asap. meanwhile Did you try removing the package completely and reinstalling it again ? and make sure you publish the config file.

also, try to change the 'number_of_digits' => 30, 8 to 30 as shown to get rid of "padded === equal to symbols" if you feel that's causing the error. I'll try to explain that reason before closing the issue.

from two-factor-authentication.

I've just checked this using Authy, and it turned out to be not working using that. However I'm not facing any issue usng Google Authenticator and worked perfectly fine. I'll work on it and update it asap.

Also @ampodobas do send me your 2fa-config.php file and specify which client app you're using, GA or Authy? so that It'll help me debug what exactly is going wrong.

from two-factor-authentication.

0.1.6 is tested and working using Google Authenticator as well as Authy with default configuration.

from two-factor-authentication.