Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
weboob
weboob
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 177
    • Issues 177
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 49
    • Merge Requests 49
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • weboob
  • weboobweboob
  • Merge Requests
  • !442

Open
Opened Feb 15, 2020 by Ludovic LANGE@llange
  • Report abuse
Report abuse

WIP: [ovh] Handle user-activated double factor authentication

  • Overview 3
  • Commits 3
  • Pipelines 10
  • Changes 3

OVH lets the user enable (or not) a 2fa, which is used during each regular login. It's now possible to manage this 2fa with 2 new (optional) config values:

  • 2fa_type let you choose the type of 2fa (between totp, sms, u2f, staticOTP)
  • 2fa_value let you handle the value of this second factor.

You have multiple options for the value of the 2fa:

  • You may let 2fa_value absent or empty, in which case weboob should ask you for the value to use at the time it is needed. You'll be able to use your TOTP (mobile) application, check your received SMS, use a security code, ...
  • You may also choose to use an external tool which will provide the value (e.g. PasswordStore with OTP extension, an SMS reading application, ...)

Note: For the moment, the 'u2f' method needs specific information sent to the key which are not available in this interface (challenge, list of registered keys). Please do not use it at this time.

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch "https://git.weboob.org/llange/weboob.git" "ovh_handle_user_2fa"
git checkout -b "llange/weboob-ovh_handle_user_2fa" FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout "origin/master"
git merge --no-ff "llange/weboob-ovh_handle_user_2fa"

Step 4. Push the result of the merge to GitLab

git push origin "master"

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: weboob/weboob!442