agreeable-microphone-83376
09/09/2022, 2:22 AM<http://api.abc.com|api.abc.com>
domain. So, all the GET/POST/DELETE request to backend to fetch data from db will be made on this sub-domain.
_Domain for authentication_: <http://auth.abc.com|auth.abc.com>
_Cookie domain_*:* <http://abc.com|abc.com>
CORS : Enabled
Question-1: Will we have to keep one more separate sub-domain for oathkeeper, on which oathkeeper will run? eg: <http://oathkeep.abc.com|oathkeep.abc.com>
or can Oathkeeper and Backend API use same sub-domain (<http://api.abc.com|api.abc.com>
)
Question-2: If we use separate sub-domain`(oathkeep.abc.com)` for Oathkeeper, then all the api requests that will be made to backend api (<http://api.abc.com|api.abc.com>)
to fetch data:
Question-2a. Will they be made first to oathkeeper sub-domain, which then checks session/authentication and redirect to upstream every time, like on each request? In this case arn't we creating a time lag at every request?
Question-2b. In this case of request first to oathkeeper sub-domain, that redirect to upstream sub-domain url, if a POST request with json data has to be made to backend api (<http://api.abc.com|api.abc.com>
), then will json be used to submitted to (<http://oathkeep.abc.com|oathkeep.abc.com>)
?high-optician-2097
high-optician-2097
magnificent-engine-41970
09/12/2022, 6:16 AMhigh-optician-2097
high-optician-2097
magnificent-engine-41970
09/12/2022, 7:32 AMhigh-optician-2097