Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #28714
     mockykid
    Participant

    Thanks!!! This helped immensely – I created a Kubernetes “LoadBalancer” service for RADIUS on udp/1812 and all looks good on the Azure side (public IP and ingress forwarding rule as expected), and on the Kubernetes the service correctly points to the backend AM port. A single command appeared to have resolved this!!!

    Having said that – my RADIUS requests are timing out with no response from the server…

    Where do I enable and access the RADIUS debugging logs on the AM server, and how do I map RADIUS requests to a specific journey that I’ve configured in the ForgeRock GUI?

Viewing 1 post (of 1 total)