I suspect a firmware upgrade probably fixes that behaviour.
I'd start by reviewing the event logs on your IAS server for reasoning as to why it's not authenticating your client.
Whilst stuffing HTTP(s) headers with custom attributes is often discouraged as the values aren’t to immediately visible.
Put the value in the body, and you’re invading the business aspect of an API with execution specific details, not to mention potentially changing the API definition.I cannot get WPA2 enterprise to work on my network. Windows Domain, using IAS and its own CA Linksys WAP200 Access Point I setup the AP to use WPA2-Enterprise Mixed using RADIUS I setup and registered IAS on the domain controller.I added the AP as a client with and have tried using both RADIUS Standard and Cisco as the RADIUS type.The book doesn’t go into the depth of details for practises that Apiary (Pro Edition) offers with style guidelines which will describe morec detailed recommended practises (more here).When configuring API Policies in the the Oracle API Platform it helps if there is a simple back end that can take the received payload and record the sent values (header & body) as well as reflect the call details back as the response, or possibly respond with a test payload (so that response policies, particularly policies that require payload navigation can be exercised correctly).