# Autologin or mutual TLS authentication in webapp **URL:** \ **Category:** Web App Development\ **Created:** [April 25, 2024, 11:43am UTC](https://forum.webostv.developer.lge.com/t/autologin-or-mutual-tls-authentication-in-webapp/6776 "2024-04-25T11:43:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mysphera](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mysphera](https://forum.webostv.developer.lge.com/u/mysphera)\ **Post date:** [April 25, 2024, 11:43am UTC](https://forum.webostv.developer.lge.com/t/autologin-or-mutual-tls-authentication-in-webapp/6776/1 "2024-04-25T11:43:57Z")
Hello, we are developing a web application for dashboard visualization. One of the problems we are seeing is that we do not know how to make the browser can authenticate in our system. Our web server runs on a wildfly and in PC environments, the user puts his username and password and access to the web, but for the dashboards, we want that when the TV starts, it authenticates on the web without the intervention of any person. For raspberry devices, we have used TLS mutual authentication with self-signed certificates and it works perfectly, but I would like to know what possibilities WebOS offers for the self authentication of a web. Would it be possible to store the user credentials and password in some memory to later use this data to proceed to login? Is it possible to use some kind of public key certificate to authenticate the TV in our system? Thank you. ---
**Author:** ![narae0.kim](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@narae0.kim](https://forum.webostv.developer.lge.com/u/narae0.kim)\ **Post date:** [April 26, 2024, 3:42am UTC](https://forum.webostv.developer.lge.com/t/autologin-or-mutual-tls-authentication-in-webapp/6776/2 "2024-04-26T03:42:39Z")
You cannot deploy your own certificates to webOS TV or webOS tools. Each webOS version has a list of trusted root certificates, and modification of this list is not allowed. For more information, please refer to [TLS and Root Certificates](https://webostv.developer.lge.com/develop/specifications/tls). Thank you. ---
**Author:** ![mysphera](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mysphera](https://forum.webostv.developer.lge.com/u/mysphera)\ **Post date:** [May 20, 2024, 11:38am UTC](https://forum.webostv.developer.lge.com/t/autologin-or-mutual-tls-authentication-in-webapp/6776/3 "2024-05-20T11:38:10Z")
Thanks narae0.kim. What mechanisms could we use so that the TV can be securely and univocally identified on our server? Our need is to authenticate the TV on our web server. How can we use RFC 8705 OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens? Thanks a lot. ---
**Author:** ![narae0.kim](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@narae0.kim](https://forum.webostv.developer.lge.com/u/narae0.kim)\ **Post date:** [May 23, 2024, 7:21am UTC](https://forum.webostv.developer.lge.com/t/autologin-or-mutual-tls-authentication-in-webapp/6776/4 "2024-05-23T07:21:56Z")
If you want to use OAuth in your app, you can use login for devices as follows: > **[For Devices - Facebook Login - Documentation - Meta for Developers](https://developers.facebook.com/docs/facebook-login/for-devices)** > > This document is for developers wanting to implement Facebook Login on apps for devices such as Smart TVs, digital photo frames, or Internet of Things devices. > **[Sign-In on TVs and Limited Input Devices  |  Authentication...](https://developers.google.com/identity/gsi/web/guides/devices)** > **[PIN-Based OAuth](https://developer.twitter.com/en/docs/authentication/oauth-1-0a/pin-based-oauth)**