Skip to content

[defect]: Server attempts Auth-Type method even when Proxy-To-Realm is set #5596

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

Open
zapotah opened this issue May 24, 2025 · 3 comments
Open
Labels
defect category: a defect or misbehaviour

Comments

@zapotah
Copy link

zapotah commented May 24, 2025

What type of defect/bug is this?

Unexpected behaviour (obvious or verified by project member)

How can the issue be reproduced?

Define a home server in proxy.conf, set Proxy-To-Realm with unlang in authorise section at the end, if some module, ie. pap sets Auth-Type along the way processing authorise section freeradius does both, proxies to the home server and tries to authenticate via ie. pap module and sends out both responses (ie. Access-Accept from proxied and Access-Reject from local pap module). This at the very least conflicts with https://wiki.freeradius.org/config/Proxy#what-happens_proxying-from-unlang in case this is somehow intended behavior.

Log output from the FreeRADIUS daemon

unnecessary

Relevant log output from client utilities

No response

Backtrace from LLDB or GDB

@zapotah zapotah added the defect category: a defect or misbehaviour label May 24, 2025
@alandekok
Copy link
Member

Which version is this for? I don't see this happening in the current releases when I test it.

@zapotah
Copy link
Author

zapotah commented May 24, 2025

Version: 3.2.7-1 from http://packages.networkradius.com/freeradius-3.2/ubuntu/jammy jammy

@alandekok
Copy link
Member

Do you have a diff or patch from the default configuration which reproduces this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect category: a defect or misbehaviour
Projects
None yet
Development

No branches or pull requests

2 participants