Forum Discussion
As I mentioned on my Azure AD intergration I do not see your issue, so this could be limited to your environment. Also for the cookie part there is really a lot of examples from F5 or in the commnity if you just search for them.
Examples. It is for portal access but you may test it to see if it works for you as well as your issue indicates that you may need to do a lot of testing. You may need to access the session variable for the landing URL in with "ACCESS::session data gest", save it to a normal irule variable as to use it in later events like HTTP_RESPONSE or HTTP_RESPONSE_RELEASE (this is when the F5 generates the response but as it is not the case with you maybe using portal access HTTP_RESPONSE could be the right event for you).
https://clouddocs.f5.com/api/irules/HTTP__cookie.html
You can trigger iRules in APM with an Agent but maybe this willl not be needed as when you want to add something to the the Response not Request then this means that the user should have passed the APM policy, but I am just sharing with you.
https://clouddocs.f5.com/api/irules/ACCESS_POLICY_AGENT_EVENT.html
Outside of that I can't suggest anything else as I am not familiar with your network environment like you are as you can see that F5 generates HTTP 301/302 redirect to the client (you can see with HTTP debuging on the client https://support.f5.com/csp/article/K35932460 ) and maybe not the cookie but as mentioned in previous messages changing the HTTP redirect could help. That is what I can share and hopefully it helps you to investigate your issue.
You - well I haven't been able to set a cookie during the initial redirect to /my.policy
cookie going to the client not the back end.
- Nikoolayy1Dec 31, 2022MVP
Cookies go to the clients not the backend as this is just how they work. For backend just set http header as there are many ways for that, so you just need a server side event like HTTP-RESPONSE . Happy New Year from me as now is not the time to do F5 stuff but to celebrate 🤩