Custom Secure Hotspot - ZD keeps returning 202 Authentication Pending

I am building a cutsom secure hotspot following the guidance in the Ruckus Tech Note "Configuring Hotspots with Secure Hotspot". When I set the HostSpot Authentication Server to anything other than "Local Database" all I get back for known valid users is a 202 Authentication Pending response. Can anyone advise on how I might resolve this? Ideally I am wanting to use an AD server for authentication and this works fine for WLANs - it is only when used in a HotSpot that it fails.

If you're following the HotSpot tech note, you'll see you need to define your login.html page on your external server too, and specify this unauthenticated URL in your configuration, and you'll need to use RADIUS in front of your AD user database for authentication.

Thanks for the response. I am not entirely sure we are quite on the same page.
Firstly, yes, that is the Tech Note I have worked from. Taking the chart on page 24 as a reference, I am getting as far as step 6. The "response-code" in the XML coming back from the Zone Director is consistently a 202 if I use AD or Radius as the Authentication Server in the HotSpot configuration; if I use Local Database I can get a successful 201 but this is obviously not much help (beyond establishing that my server-side code is working). I get the same response when I use a request generating tool such as "PostMan", so I know I am sending the XML to the ZoneDirector correctly and I am getting valid XML back. I just don't understand why credentials known to be good (and tested in the AAA config page) are producing the 'Authentication Pending' response.

Am I missing a crucial point in your response (or in the tech note) or did I not make clear in my original post just how far I am getting? I would appreciate any further help you might be able to offer.