Re: 2FA not showing QR

2022-01-20 Thread Don Eugene Paul Viado
 HI,
I got it to work.  So I realized I was still using old extension 
guacamole-auth-totp-1.2.0.  This seems to work fine on 1.3.0 but after 1.4.0 it 
doesn't seem to present the QR anymore on newly added users.  If you have 
already activated your token, it will still work as usual but adding new users 
and having them register it on their device with a presented QR does not 
happen.  It will say that multi factor is enabled and immediately asked for 
code.  Upgrading this extension to 1.4.0 fixed the issue.  Thanks.
On Thursday, 20 January 2022, 03:36:50 pm SGT, Mike Jumper 
 wrote:  
 
 On Wed, Jan 19, 2022, 22:05 Don Eugene Paul Viado  
wrote:

Hi,
When in 1.3.0, when a new user created they can login with initial password and 
if 2FA is activated they are presented with QR code to enroll in device.  This 
doesn't work now in 1.4.0.  Does anyone have the same issue and can you please 
advise how it is fixed?

Can you provide any more detail? How is it not working, specifically? Are you 
seeing an enrollment prompt that's missing a QR code, or is it as if TOTP isn't 
enabled at all? What other extensions are installed?
- Mike
  

Re: 2FA not showing QR

2022-01-19 Thread Mike Jumper
On Wed, Jan 19, 2022, 22:05 Don Eugene Paul Viado 
wrote:

> Hi,
>
> When in 1.3.0, when a new user created they can login with initial
> password and if 2FA is activated they are presented with QR code to enroll
> in device.  This doesn't work now in 1.4.0.  Does anyone have the same
> issue and can you please advise how it is fixed?
>

Can you provide any more detail? How is it not working, specifically? Are
you seeing an enrollment prompt that's missing a QR code, or is it as if
TOTP isn't enabled at all? What other extensions are installed?

- Mike


2FA not showing QR

2022-01-19 Thread Don Eugene Paul Viado
Hi,
When in 1.3.0, when a new user created they can login with initial password and 
if 2FA is activated they are presented with QR code to enroll in device.  This 
doesn't work now in 1.4.0.  Does anyone have the same issue and can you please 
advise how it is fixed?
Thanks