Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable HOTP event window #34

Closed
sj opened this issue Feb 17, 2014 · 4 comments
Closed

Configurable HOTP event window #34

sj opened this issue Feb 17, 2014 · 4 comments
Labels

Comments

@sj
Copy link

sj commented Feb 17, 2014

Hi,

It's not quite clear what the plugin's HOTP event window is. It's probably dictated by multiotp? I'd like to be able to configure that in the administrator interface.

Thanks!

Bas

@loki36
Copy link
Owner

loki36 commented Feb 25, 2014

Hi,
I'm not sure to understand the question can you send a screenshot

@sj
Copy link
Author

sj commented Feb 25, 2014

I've explained it in the last few sentences (section titled "Explanation of HOTP Authentication events and the event window") on http://www.sj-vs.net/two-factor-authentication-for-owncloud-using-one-time-passwords-otp-from-yubikey/ - you can have a look if you like?

I think multiotp uses the _config_data['max_event_window'] variable to set it, with a default of 100.

@loki36
Copy link
Owner

loki36 commented Feb 25, 2014

so,
you want have for HOTP, two config,
the last event window
and
the event window range
??
if yes i will create a new issue, but i don't know for what milestone

@sj
Copy link
Author

sj commented Feb 25, 2014

Indeed: the 'last event' will indicate where the window starts, the 'window size' (or 'window range') will determine how many 'future' HOTP values will be checked. Currently, the 'last event' is also used for the TOTP time window size (defaults to 30 for Google Authenticator), which is slightly confusing since these are very different things. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants