The Repository allows you to store endpoint information from queries triggered by other processes - most commonly DHCP Profiling. There is a lot of useful endpoint specific information that comes as a part of the DHCP Request, but obviously DHCP will not process every time AAA does. There are also many other options for storing and manipulating the Endpoint Repository database, apart from an actual AAA request.
The per AAA Request or AAA Accounting packets may not contain the details you need.
------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
------------------------------
Original Message:
Sent: Mar 04, 2024 10:24 AM
From: Ahmad Enaya
Subject: Endpoint vs Authorization:[Endpoints Repository]
When adding [Endpoint Repository] as an authorization source, I have the option to build policies and role mapping based on Endpoint or based on Authorization:[Endpoints Repository]. Most of the options are the same for both options, so what is the difference and why I would use one and not the other?
If Endpoint option is available even without adding [Endpoints Repository] as an authorization source, is there any reason to add [Endpoints Repository] as an authorization source or even enable authorization?
