# Take a look at this!

**URL:** <https://community.glideapps.com/t/take-a-look-at-this/26995>\
**Category:** Project Showcase\
**Created:** [May 19, 2021, 9:30pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995 "2021-05-19T21:30:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![WolfGamer](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wolfgamer/32/25796_2.png) [@WolfGamer](https://community.glideapps.com/u/WolfGamer)\
**Post date:** [May 19, 2021, 9:30pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/1 "2021-05-19T21:30:12Z")

</div>

I made a small login page and I wanted to ask if I can integrate it with my Glide App?  
Link - [https://express-login-system.kingbob2.repl.co/](https://express-login-system.kingbob2.repl.co/)

---

<div class="post-metadata">

**Author:** ![AyS\_0908](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ays_0908/32/27349_2.png) [@AyS\_0908](https://community.glideapps.com/u/AyS_0908)\
**Post date:** [May 19, 2021, 9:50pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/2 "2021-05-19T21:50:23Z")

</div>

Probably via a webview component

---

<div class="post-metadata">

**Author:** ![WolfGamer](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wolfgamer/32/25796_2.png) [@WolfGamer](https://community.glideapps.com/u/WolfGamer)\
**Post date:** [May 19, 2021, 9:51pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/3 "2021-05-19T21:51:08Z")

</div>

Isn’t that only for premium users?  
@AyS_0908

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [May 19, 2021, 11:10pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/4 "2021-05-19T23:10:16Z")

</div>

Is there a reason you don’t want to use the native Glide login?

---

<div class="post-metadata">

**Author:** ![WolfGamer](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/wolfgamer/32/25796_2.png) [@WolfGamer](https://community.glideapps.com/u/WolfGamer)\
**Post date:** [May 19, 2021, 11:40pm UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/5 "2021-05-19T23:40:43Z")

</div>

I want a actual password so users feel safe!

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [May 20, 2021, 12:02am UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/6 "2021-05-20T00:02:41Z")

</div>

I don’t think there’s a good way you can bypass the Glide login without making your app public and expose your data. Still, even with a public app, users can login, so it might make your app confusing.

I would stick with what Glide provides, email authentication either via Google or PINs are good.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [May 20, 2021, 4:14am UTC](https://community.glideapps.com/t/take-a-look-at-this/26995/7 "2021-05-20T04:14:04Z")

</div>

> [@WolfGamer](#):
>
> I want a actual password so users feel safe!

What makes you think that will make users feel safe?  
SSO is ubiquitous these days - when I sign up for a cloud based service I’ve come to expect that I can just sign up and authenticate with my Google (or whatever) account.  
It’s convenient, and I know it’s probably secure, as OAuth2 is an industry standard.  
If a website or service asks me to set a separate password, I’m immediately suspicious and am more likely to just not bother. I have no idea if the password I provide will be securely handled and stored, and generally I’d prefer not to take the risk. At the very least, it tells me that the developers have been lazy in not supporting any form of SSO.
