Skip to content

[Feature Proposal] Internxt: add ability to optionally use 2fa secret instead of 2fa code. #9528

Description

@Adelzu

The associated forum post URL from https://forum.rclone.org

https://forum.rclone.org/t/use-internext-otp-secret-instead-of-totp-code/53932

What is your current rclone version (output from rclone version)?

rclone v1.74.2

  • os/version: debian 12.11 (64 bit)
  • os/kernel: 6.12.91-production+truenas (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.26.3
  • go/linking: static
  • go/tags: none

What problem are you are trying to solve?

Internxt authorization is not reliable when 2fa is in use.
Proposed solution is to have rclone ask for 2fa secret (seed) first if needed, if blank, it will resume the normal flow. If given the seed, rclone will generate the 2fa code automatically and use the secret to regenerate when needed. Secret must be obscured and stored in the config file.

How do you think rclone should be changed to solve that?

I have the changes ready and tested. Will push a PR to close this feature request.
Minimal Changes to 2 files related to Internxt integration.

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions