Skip to content
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.

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

Do not use null domain in auth credentials #8498

Merged
merged 1 commit into from
May 28, 2024

Conversation

thc202
Copy link
Member

@thc202 thc202 commented May 28, 2024

Use an empty string for the domain when creating the auth credentials as null is not allowed.

Use an empty string for the domain when creating the auth credentials
as null is not allowed.

Signed-off-by: thc202 <thc202@gmail.com>
@thc202 thc202 added the bug label May 28, 2024
@thc202 thc202 added this to the 2.16.0 milestone May 28, 2024
thc202 added a commit to thc202/zap-extensions that referenced this pull request May 28, 2024
Set an empty realm instead, as null is not allowed and would break the
authentication.

Related to zaproxy/zaproxy#8498.

Signed-off-by: thc202 <thc202@gmail.com>
thc202 added a commit to thc202/zap-extensions that referenced this pull request May 28, 2024
Check that the user actually has an auth state before trying to use it,
which could happen if the auth attempt lead to an error.

Related to zaproxy/zaproxy#8498.

Signed-off-by: thc202 <thc202@gmail.com>
@kingthorin kingthorin merged commit ea1572f into zaproxy:main May 28, 2024
10 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 28, 2024
@thc202 thc202 deleted the non-null-realm branch May 28, 2024 10:30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging this pull request may close these issues.

None yet

3 participants