Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 4 subscribers
  • Views 2399 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RADIUS authentication for web filtering

Ysk St

When using RADIUS for backend server, web filtering authentication fails without a policy defined 'Radius Users.'
When using Active Directory for backend server, web filtering authentication successes with 'Base Policy' only.
UTM firmware is 9.352.
I think authentication should work without additional policies when using RADIUS as same as using AD.

Is this a bug or design?
If it is design, could you explain the reason and show me the document or KB regarding this?



This thread was automatically locked due to age.
  • 0

    Hi, and welcome to the UTM Community!

    I've never seen RADIUS used for authentication in Web Protection. I don't see any indication that it's supported there except perhaps for Backend Groups used to assign Filter Actions in Group Policies.  I would not use RADIUS auth there though.

    In fact, in Web Filtering, authentication with AD-SSO doesn't use the AD server defined on the 'Servers' tab - AD-SSO configuration is done separately on the 'Single Sign-On' tab.  The server defined on the 'Servers' tab is only used in Web Filtering for determining Backend Group membership.  There are other places where either or both can be used for authentication.

    If you're successful sometimes in using AD-SSO, but not others, please insert pictures of the Policies open in Edit.

    Cheers - Bob