@gjain-sag Thank you for raising this topic! Even though we don't support direct migration from WF dist (and the old Operator) to Quarkus dist (and the new Operator), I believe it is still a valid use case to have the possibility to use /auth relative path. Otherwise we would force the users to actually update their apps to use a new address which would introduce additional migration costs and is not strictly necessary.

Created #12100.

Before tackling this Issue I would like to hear more opinions on this one, I believe that @pedroigor and I are more inclined to drop the support instead.

Thanks @andreaTP ,

We have many dependent applications which are using our client for authentication and other configurations. Removing support for "/auth" will create backward compatibility issues for us.

In our case we have one reverse proxy TLS endpoint for one public sub domain, serving all calls to different backends based of url path. Removing /auth would require an additional public sub domain just for the keycloak part.

At the end it's just more PKI and system maintainance for nothing.