redirect URL port prevents successful authentication

Created on 19 September 2024, 3 months ago

Problem/Motivation

We recently implemented PaloAlto Prisma Cloud as WAF in our environment and the agent is installed on the web host. It ingests all traffic from port 1234 and sends it to port 443. Our bindings are reflecting this configuration.

In OpenID Connect settings page, the redirect Url is determined to be https://mysite.com:1234/openid-connect/{client_name} but as you know, this information is read only.

The problem it creates is that when a successful authentication happens, users get redirected to https://mysite.com:1234/openid-connect/{client_name} which ends up timing out since the port is not exposed (nor do we want to expose it). If I remove the port from the address, it goes through fine and the authentication happens.

I would like for the redirect URL to be made on a different port or to be able to store a custom redirect URL.

I understand this is an odd case which doesn't necessarily warrant any code update but I wanted to see if you guys had any ideas how I can make it work.

πŸ’¬ Support request
Status

Active

Version

1.4

Component

Miscellaneous

Created by

πŸ‡ΊπŸ‡ΈUnited States nixar San Antonio, TX

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024