Feature/move pre process filter

[fdurand]

Description

Added the ability to rewrite the username of the radius request based on the radius prePRocess filter.

Impacts

• RADIUS authorize workflow

Delete branch after merge

YES

Checklist

• Document the feature
• Add unit tests
• Add acceptance tests (TestLink)

NEWS file entries

Enhancements

• Rewrite the username of the request from radius preProcess filter

[nqb]

I understand the logic.

However, in current state, if you build a RADIUS attribute on the fly to use it as a username, you will have following behavior:

• logic related to machine_account still use username detected before
• logger will display wrong information (handling autz ..)

[nqb]

These changes allow us to rewrite username on the fly based on a RADIUS filter in preProcess scope.

However, it seems that it's not possible to modify RADIUS attributes in a RADIUS request and have them be taken into account by PacketFence later. I don't see a simple way to create a connection profile using an Advanced Filter to filter on RADIUS attributes.

[nqb]

@jrouzierinverse, is it possible to use an advanced filter like radius_request.Calling-Station-Id == 192.168.0.1 on a connection profile ?