Skip to main content
EOS.IO

Return to Question

Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
added 13 characters in body
Source Link
Phillip Hamnett - EOS42
Phillip Hamnett - EOS42
  • 4.7k
  • 1
  • 14
  • 57

i gotI had the the idea of ana secure alternative login process using an eosEOS smart contract instead usingof firebase or amazonAmazon cognito. I would like to know if something like this feasible?

My idea is somewhat like.

  1. serverServer creates cookie with a specific id
  2. serverServer sends cookie with id to client
  3. clientClient gets cookie with unique id from server
  4. clientClient wants to login so he executes a action "Login" from contract and writes the id he got formfrom the server in the form of a hash256SHA256 hash in the contract (contract writes the timestamp of execution also in the table)
  5. client sendClient sends message to the server when the action was successful that he wants to login.
  6. serverServer looks up the eosEOS contract table up for the name and if the entry is not older than 1-2sec and checks if the hashed id is the same as the server gave to the client.
  7. isIf everything is ok, the client gets a session and can see his private data or whatever the website returns.

(server could be something like node.js with express-session and reactjs/vue/angular as front-end)

iI don't know if this is a secure way to do this or an alternative for firebase auth and amazon cognito. I would also be interested in other thoughts,how how one could realize something like that.

i got the the idea of an secure alternative login process using an eos smart contract instead using firebase or amazon cognito. I would like to know if something like this feasible?

My idea is somewhat like.

  1. server creates cookie with a specific id
  2. server sends cookie with id to client
  3. client gets cookie with unique id from server
  4. client wants to login so he executes a action "Login" from contract and writes the id he got form server in form of a hash256 in the contract (contract writes the timestamp of execution also in the table)
  5. client send message to the server when the action was successful that he wants to login.
  6. server looks the eos contract table up for the name and if the entry is not older than 1-2sec and checks if the hashed id is the same as the server gave to the client.
  7. is everything ok, the client gets a session and can see his private data or whatever the website returns.

(server could be something like node.js with express-session and reactjs/vue/angular as front-end)

i don't know if this is a secure way to do this or an alternative for firebase auth and amazon cognito. I would also be interested in other thoughts,how one could realize something like that.

I had the the idea of a secure alternative login process using an EOS smart contract instead of firebase or Amazon cognito. I would like to know if something like this feasible?

My idea is somewhat like.

  1. Server creates cookie with a specific id
  2. Server sends cookie with id to client
  3. Client gets cookie with unique id from server
  4. Client wants to login so he executes a action "Login" from contract and writes the id he got from the server in the form of a SHA256 hash in the contract (contract writes the timestamp of execution also in the table)
  5. Client sends message to the server when the action was successful that he wants to login.
  6. Server looks up the EOS contract table for the name and if the entry is not older than 1-2sec and checks if the hashed id is the same as the server gave to the client.
  7. If everything is ok, the client gets a session and can see his private data or whatever the website returns.

(server could be something like node.js with express-session and reactjs/vue/angular as front-end)

I don't know if this is a secure way to do this or an alternative for firebase auth and amazon cognito. I would also be interested in other thoughts, how one could realize something like that.

Source Link
Mangooxx
Mangooxx
  • 341
  • 1
  • 8

A possible alternative sign in/login process instead of firebase auth / amazon cognito using an eos contract?

i got the the idea of an secure alternative login process using an eos smart contract instead using firebase or amazon cognito. I would like to know if something like this feasible?

My idea is somewhat like.

  1. server creates cookie with a specific id
  2. server sends cookie with id to client
  3. client gets cookie with unique id from server
  4. client wants to login so he executes a action "Login" from contract and writes the id he got form server in form of a hash256 in the contract (contract writes the timestamp of execution also in the table)
  5. client send message to the server when the action was successful that he wants to login.
  6. server looks the eos contract table up for the name and if the entry is not older than 1-2sec and checks if the hashed id is the same as the server gave to the client.
  7. is everything ok, the client gets a session and can see his private data or whatever the website returns.

(server could be something like node.js with express-session and reactjs/vue/angular as front-end)

i don't know if this is a secure way to do this or an alternative for firebase auth and amazon cognito. I would also be interested in other thoughts,how one could realize something like that.