Symptoms
UCCX does not natively protect HTTP Triggers.
Diagnosis
I wanted to come up with a solution to handle HTTP cookie based authentication.
Solution
There is a zip file for this project attached to this article. It was written on UCCX 12.5(1).
Before HTTP Authentication
![uccx-http-triggered-application-code.png uccx-http-triggered-application-code.png](https://community.cisco.com/t5/image/serverpage/image-id/100707i8F123D6E5CA3CD87/image-size/large?v=v2&px=999)
![uccx-http-triggered-application-result.png uccx-http-triggered-application-result.png](https://community.cisco.com/t5/image/serverpage/image-id/100710iC39E16224D892FE2/image-size/large?v=v2&px=999)
After HTTP Authentication
![uccx-http-triggered-application-with-auth-code.png uccx-http-triggered-application-with-auth-code.png](https://community.cisco.com/t5/image/serverpage/image-id/100719i1CE6D284E910FF60/image-size/large?v=v2&px=999)
![uccx-http-triggered-application-with-auth-result-pre.png uccx-http-triggered-application-with-auth-result-pre.png](https://community.cisco.com/t5/image/serverpage/image-id/100716i8F39CC00A37B4D81/image-size/large?v=v2&px=999)
![uccx-http-triggered-application-with-auth-result-post.png uccx-http-triggered-application-with-auth-result-post.png](https://community.cisco.com/t5/image/serverpage/image-id/100717i2D673B75DE62FA60/image-size/large?v=v2&px=999)