Enable Session Persistence with Sticky Cookies

Enable persistent sessions using cookies in an App Gateway. The sticky cookie is forwarded to the same backend server.

You only need to use sticky support when you have multiple origins, and you do this by creating a NGINX upstream block .

1. Enable the sticky module in App Gateway by editing the file /usr/local/nginx/conf/nginx.conf.
   • Below the line load_module /scratch/oracle/cloudgate/home/lib/idcs_cloudgate_ngx.so;, add

     load_module /scratch/oracle/cloudgate/home/lib/ngx_http_sticky_module.so;

   • Below the line include /usr/local/nginx/conf/agent_conf/*.conf;, add

     include /usr/local/nginx/conf/origin_conf/*.conf;

2. Create a NGINX upstream block using

   $ vi /usr/local/nginx/conf/origin_conf/myupstream.conf
   
   Add below entry to myupstream.conf
   upstream weblogic {
       sticky;
       server 100.111.190.221:7003;
       server 100.111.190.220:7003;
   }

3. Change the origin server.
   1. Open the navigation menu  and select Identity & Security. Under Identity, select Domains.
   2. Click the name of the identity domain that you want to work in. You might need to change the compartment to find the domain that you want. Then, click Security and then App gateways.
   3. Under Resources select Apps, and select the App gateway.
   4. In the App details, modify the Origin server to point to the upstream.

upstream {
  sticky;  
  server 127.0.0.1:9001;
  server 127.0.0.1:9002;
}

  sticky [hash=index|md5|sha1] [no_fallback]
       [name=route] [domain=.example.com] [path=/] [expires=1h] [secure] [httponly];
   or
  sticky [hmac=md5|sha1 hmac_key=<foobar_key>] [no_fallback]
       [name=route] [domain=.example.com] [path=/] [expires=1h] [secure] [httponly];
   or
  sticky [text=raw] [no_fallback]
       [name=route] [domain=.example.com] [path=/] [expires=1h] [secure] [httponly];