Proxying REST Backends

I have several backend services (REST+SOAP) that have to be consumed by a SPA (Single Page Angular2 App). As JWT (JSON Web Token) is not feasible for me for the moment, security is done using CAS Central Authentication Service ( single sign-on protocol ). In order to avoid CORS (Cross-Origin Resource Sharing) and to have security in one place, I am thinking of creating a layer that will be accessible directly by the client and from that layer make each REST call. Something like a proxy that will just pass through the client requests. This, I see as a custom API Gateway pattern implementation as I am not using an API Management tool. Do you see any disadvantages to this solution?

May 7, 2025 - 15:35

I have several backend services (REST+SOAP) that have to be consumed by a SPA (Single Page Angular2 App).

As JWT (JSON Web Token) is not feasible for me for the moment, security is done using CAS Central Authentication Service ( single sign-on protocol ).

In order to avoid CORS (Cross-Origin Resource Sharing) and to have security in one place, I am thinking of creating a layer that will be accessible directly by the client and from that layer make each REST call. Something like a proxy that will just pass through the client requests.

This, I see as a custom API Gateway pattern implementation as I am not using an API Management tool.

Do you see any disadvantages to this solution?