Custom ergw_aaa handler for location checking

[javiermtorres]

CAPWAP needs to retrieve a Location element from an HTTP service and add it to its RADIUS requests (LI-Location). This item is already present in the dictionaries for ergw_aaa.

A custom handler has to be developed that makes the HTTP call, retrieves the Location element and adds it to the session so that the ergw_aaa handler can send it forward.

[RoadRunnr]

That handler should never, ever become a part of ergw_aaa. Make it a standalone App or borrow ergw_sbi, but ergw_aaa is the wrong place for this.

[javiermtorres]

No, it won't. It will be just a module from capwap called from a specific step in the same procedure where the RADIUS request is sent. What I mean is that this step will include in the session the attribute that will be sent in the RADIUS request.

[RoadRunnr]

That still sounds like you want to use the ergw_aaa_session mechanism. And that should not be done at all.

[javiermtorres]

No, it'd be by configuration. The ergw_aaa_session would not be modified either.

        {session, ['Default']},
        {procedures, [
          {authenticate, ['Load-Location', 'RADIUS-Auth-Station']},
          {authorize, []},
          {start,   ['Load-Location', 'RADIUS-Acct-Station']},
          {interim, ['Load-Location', 'RADIUS-Acct-Station']},
          {stop,    ['Load-Location', 'RADIUS-Acct-Station']}
        ]}