Here I have sketched the current use cases of Ethora Chat Components in terms of Users authentication.
Use Case 2 (hard-coded or temporary accounts):
B: Use hard-coded user ID.
Everybody who use the app will automatically log in with the same user ID. All messages in the chat room will be from the same user.
Use for: demo purposes or project where multiple user accounts are not required (e.g. anonymous chat / comments section).
A: Use randomly generated temporary user ID.
No login screen required, but User gets a random account and that account will not persist as login and password is not given to the User. Next time User opens the app, it will be a new random account generated for them.
Use for: demo purposes, projects where users should be anonymous and don't need to persist across sessions. Also for projects where temporary chat rooms are used for each new session. For example, AI assistant where it will be just User and AI Bot with a fresh context every time. This can work for web page visitors where login is not required.
Use Case 1:
Using Login screen from Chat Component.
Useful when you don't have a legacy users sign-up system and you need the app to on-board users for you.
You will be using either:
* Ethora signup / login system via e-mail + password
* Ethora SSO login/sign-up (Google, Facebook, Apple etc)
Your Users will be shown the Login screen where they can either sign up for a new account, or log in with an existing account.
No backend work required on your side.
No App Secret stored in your frontend. App ID is stored in your frontend config file.
You download App config file in JSON format.
Use Case 3: Using User IDs from External/Legacy System.
Your existing System backend communicates to Dappros backend when new Users are Created or Deleted. Users sign on via your system as normal. Your system passes User ID to chat component which verifies it via its own Authentication module.
3.1. build custom looking at Ethora API
3.2. look at backend code sample from Ethora (PHP, Node.js, Python)
3.3. use existing plugin from Ethora (Wordpress, Shopify etc - if exists)
Question
TarasFilatov
Here I have sketched the current use cases of Ethora Chat Components in terms of Users authentication.
Use Case 2 (hard-coded or temporary accounts):
B: Use hard-coded user ID.
Everybody who use the app will automatically log in with the same user ID. All messages in the chat room will be from the same user.
Use for: demo purposes or project where multiple user accounts are not required (e.g. anonymous chat / comments section).
A: Use randomly generated temporary user ID.
No login screen required, but User gets a random account and that account will not persist as login and password is not given to the User. Next time User opens the app, it will be a new random account generated for them.
Use for: demo purposes, projects where users should be anonymous and don't need to persist across sessions. Also for projects where temporary chat rooms are used for each new session. For example, AI assistant where it will be just User and AI Bot with a fresh context every time. This can work for web page visitors where login is not required.
Use Case 1:
Using Login screen from Chat Component.
Useful when you don't have a legacy users sign-up system and you need the app to on-board users for you.
You will be using either:
* Ethora signup / login system via e-mail + password
* Ethora SSO login/sign-up (Google, Facebook, Apple etc)
Your Users will be shown the Login screen where they can either sign up for a new account, or log in with an existing account.
No backend work required on your side.
No App Secret stored in your frontend. App ID is stored in your frontend config file.
You download App config file in JSON format.
Use Case 3:
Using User IDs from External/Legacy System.
Your existing System backend communicates to Dappros backend when new Users are Created or Deleted. Users sign on via your system as normal. Your system passes User ID to chat component which verifies it via its own Authentication module.
3.1. build custom looking at Ethora API
3.2. look at backend code sample from Ethora (PHP, Node.js, Python)
3.3. use existing plugin from Ethora (Wordpress, Shopify etc - if exists)
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.