ory / ory/hydra

The current challenge is too long and may be mistakenly identified as risky by the browser

Open
#3,955 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
17.6k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Preflight checklist
Ory Network Project

No response

Describe the bug

The current challenge is too long and may be mistakenly identified as risky by the browser.

The challenge of v2.x is more than 1,000 characters, while the original challenge of v1.x is only a few dozen characters.

Is there a way to make the challenge shorter? I haven't found any place in the document to configure it.

Image

Reproducing the bug

Occasional, may not always recur

Relevant log output

Relevant configuration

Version

2.2.0

On which operating system are you observing this issue?

macOS

In which environment are you deploying?

Kubernetes

Additional Context

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the occasional behavior described for Hydra v2.2.0 on macOS and Kubernetes, then read the issue discussion for context on how the v2.x challenge is generated and configured. Done means the challenge is shorter and no longer mistaken for risky by the browser, with the relevant behavior covered by verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.