Skip to content

SSO Domain Verification Expiring After A Week #4051

@kannasama

Description

@kannasama

Steps To Reproduce

  1. Go to 'Organization' > 'Settings' > 'Domain verification'
  2. Add a domain entry, e.g. yourdomain.com.
  3. Complete initial verification.
  4. After approximately a week, the record is removed.

Expected Result

Domain verification to complete automatically on a regular basis.

Actual Result

Domain verification is removed after approximately one week. This can be extended by manually triggering the verification process.

Screenshots or Videos

No response

Additional Context

It appears that the the automated process to actually trigger the verification check does not occur. If there were an API call, or URL that could be called where a scheduled task could be configured to run this, I would be fine with that. That said, this is something that should be handled in an automated process.

Additionally, while I can understand the need for domain verification in hosted solutions, perhaps some option could be available to exempt self-hosted, single organization instances from this requirement for SSO.

Githash Version

1e3e937-dirty

Environment Details

No response

Database Image

No response

Issue-Link

#2480

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugbw-unified-deployAn Issue related to Bitwarden unified deployment

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions