Project

General

Profile

Bug #7528

Captive Portal caches user RADIUS credentials inconsistently with needs/described behavior

Added by Jim Pingle over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Captive Portal
Target version:
Start date:
05/08/2017
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

Captive Portal has to cache the user credentials for RADIUS Reauthentication to function, and it does not need to cache RADIUS credentials when Reauthentication is disabled. They are never cached for local users.

To me, I have a patch.

Associated revisions

Revision d4e42c54 (diff)
Added by Jim Pingle over 3 years ago

Only cache CP RADIUS Auth credentials when reauthentication is enabled. Fixes #7528

Revision ed44d5fb (diff)
Added by Jim Pingle over 3 years ago

Only cache CP RADIUS Auth credentials when reauthentication is enabled. Fixes #7528

(cherry picked from commit d4e42c54a2b7d9c955b11ad3034a186a73159f1a)

Revision 1f3b7a9e (diff)
Added by Jim Pingle over 3 years ago

Only cache CP RADIUS Auth credentials when reauthentication is enabled. Fixes #7528

(cherry picked from commit d4e42c54a2b7d9c955b11ad3034a186a73159f1a)
(cherry picked from commit ed44d5fb36f1f69196417e3feab2a9d6df4a47c8)

History

#1 Updated by Jim Pingle over 3 years ago

  • Description updated (diff)

#2 Updated by Jim Pingle over 3 years ago

  • Status changed from Assigned to Feedback
  • % Done changed from 0 to 100

#3 Updated by Jim Pingle about 3 years ago

  • Status changed from Feedback to Resolved

#4 Updated by Jim Pingle about 3 years ago

  • Target version changed from 2.4.0 to 2.3.4-p1

Also available in: Atom PDF