# Client Certificates for authentication on HTTPS request

**URL:** <https://forum.inductiveautomation.com/t/client-certificates-for-authentication-on-https-request/91016>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 28, 2024, 3:10pm UTC](https://forum.inductiveautomation.com/t/client-certificates-for-authentication-on-https-request/91016 "2024-05-28T15:10:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 28, 2024, 3:13pm UTC](https://forum.inductiveautomation.com/t/client-certificates-for-authentication-on-https-request/91016/2 "2024-05-28T15:13:14Z")

</div>

Neither scenario is supported in a first class way.

The outbound HTTP calls are possible if you go straight to Java APIs instead. There's an example in [this post](https://forum.inductiveautomation.com/t/ssl-cert-auto-renew-module/83433) where someone else got it working. This isn't something we document anywhere.

---

_[View the full topic](https://forum.inductiveautomation.com/t/client-certificates-for-authentication-on-https-request/91016)._