Skip to content

PYIC-8547: Successful callbacks must come from the mobile download page #2122

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.

Sign up for GitHub

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

Jump to bottom
Draft
MikeCollingwood wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

PYIC-8547: Successful callbacks must come from the mobile download page #2122

MikeCollingwood wants to merge 1 commit into from

Conversation

@MikeCollingwood
Copy link
Contributor

@MikeCollingwood MikeCollingwood commented Jul 16, 2025 •
edited by atlassian bot
Loading

Proposed changes

What changed

  • Enforce: Successful callbacks must come from the mobile download page to cause a state transition.

Why did it change

  • Unintended functionality we should control.

Issue tracking

Checklists

  • READMEs and documentation up-to-date
  • Browser/ unit/ Selenium tests have been written/ updated
  • No risk of exposure: PII, credentials, etc through logs/ code
  • Ensure added/updated routes have CSRF protection if required

@MikeCollingwood MikeCollingwood changed the title BAU: Successful callbacks must come from the mobile download page to … PYIC-8547: Successful callbacks must come from the mobile download page to … Jul 17, 2025
@MikeCollingwood MikeCollingwood changed the title PYIC-8547: Successful callbacks must come from the mobile download page to … PYIC-8547: Successful callbacks must come from the mobile download page Jul 17, 2025
@MikeCollingwood
Copy link
Contributor Author

MikeCollingwood commented Jul 17, 2025

/journey/next isn't a url

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@MikeCollingwood