Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Email links need email_links.default_origin (or allowed_origins)

Open Beginner friendly
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
yaml
Domain
documentation

Research direction

The issue describes a required configuration update for email links. Look for documentation files related to user configuration, email settings, or bundle setup. Update the configuration examples to include the new email_links.default_origin and allowed_origins fields. Verify the changes by checking any related configuration guides or README files.

Written by the indexing model from the issue text.

Description

documentation

Source: components-web-app/api-components-bundle#316

New required configuration for any application that sends user emails with links (password reset, email verification, new-email confirmation, welcome, account enabled):

silverback_api_components:
    user:
        email_links:
            default_origin: 'https://www.example.com'   # scheme://host[:port]
            allowed_origins: ['https://app\.example\.com']  # optional, anchored regexes
  • The request's Origin/Referer is used only when it matches allowed_origins; otherwise default_origin; with neither, no email is sent and the request is a 400.
  • A path from redirect_path_query must be a plain relative path; anything else falls back to the configured redirect path.
  • Upgrade note: without this config every email carrying a link is refused with a 400.
  • Patterns are anchored by the bundle, unlike Nelmio's origin_regex, so don't copy CORS_ALLOW_ORIGIN without checking it.
Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.