# iHost cast security issue on chrome mobile

**URL:** <https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419>\
**Category:** eWeLink CUBE\
**Created:** [October 24, 2023, 10:58pm UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419 "2023-10-24T22:58:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Domenico](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Domenico](https://forum.ewelink.cc/u/Domenico)\
**Post date:** [October 24, 2023, 10:58pm UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/1 "2023-10-24T22:58:20Z")

</div>

I have one cast with pin code setted. If I open on my pc [http://ihost.local/cast/](http://ihost.local/cast/), I can see my cast and if I click on it, the window asking me for the pin code is shown.  
If I open on my pc [http://ihost.local/cast/detail](http://ihost.local/cast/detail), It sends me to the [http://ihost.local/cast/](http://ihost.local/cast/)  
However, if I do it on Chrome mobile, of my phone, it lets me log in without problems

---

<div class="post-metadata">

**Author:** ![eerke](https://avatars.discourse-cdn.com/v4/letter/e/eb9ed0/32.png) [@eerke](https://forum.ewelink.cc/u/eerke)\
**Post date:** [October 24, 2023, 11:48pm UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/2 "2023-10-24T23:48:17Z")

</div>

Just checked. On iOS Chrome it is asking me for a PIN. Is yours an android phone?

---

<div class="post-metadata">

**Author:** ![Domenico](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Domenico](https://forum.ewelink.cc/u/Domenico)\
**Post date:** [October 25, 2023, 10:16pm UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/3 "2023-10-25T22:16:06Z")

</div>

Yes, on android phone

---

<div class="post-metadata">

**Author:** ![Domenico](https://avatars.discourse-cdn.com/v4/letter/d/8e7dd6/32.png) [@Domenico](https://forum.ewelink.cc/u/Domenico)\
**Post date:** [October 25, 2023, 10:20pm UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/4 "2023-10-25T22:20:51Z")

</div>

Let me explain better, if I open the url [http://ihost.local/cast/detail](http://ihost.local/cast/detail) on Chrome mobile on my phone (Android), it opens it without asking me for the pin and shows me the cast

---

<div class="post-metadata">

**Author:** ![Daniel\_Zhan](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/daniel_zhan/32/622_2.png) [@Daniel\_Zhan](https://forum.ewelink.cc/u/Daniel_Zhan)\
**Post date:** [November 16, 2023, 6:56am UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/5 "2023-11-16T06:56:51Z")

</div>

> [@Domenico](#):
>
> [http://ihost.local/cast/detail](http://ihost.local/cast/detail),

Thanks for your report, we will evaluate this issue to see how to improve.

---

<div class="post-metadata">

**Author:** ![lucifere](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lucifere](https://forum.ewelink.cc/u/lucifere)\
**Post date:** [January 28, 2024, 9:52am UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/6 "2024-01-28T09:52:43Z")

</div>

@ewelink, It is very important to be implemented the option to have a choice between a PIN and a password similar to .htacess (serverside pass) for CAST funtionality. At the moment, the option for Security system behavior of IHOST is pointless, it was need of something more serious than PIN for Cast access (this option must be choose by admin only in specific cases).

---

<div class="post-metadata">

**Author:** ![Teki](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/teki/32/1161_2.png) [@Teki](https://forum.ewelink.cc/u/Teki)\
**Post date:** [January 29, 2024, 8:41am UTC](https://forum.ewelink.cc/t/ihost-cast-security-issue-on-chrome-mobile/23419/7 "2024-01-29T08:41:27Z")

</div>

Considering that iHost is mostly used as a local device on the LAN, for quick access, CAST does not add a PIN function. In the future we will consider adding.
