make common login mechanism through ember simple auth

mjobuda commented 4 years ago

https://gitlab.com/owsikowski/gdates/-/issues/9

jbrainz commented 3 years ago

can i start working on this? is it still open?

mjobuda commented 3 years ago

Yes! And feel free to ask me for help. That's an important issue, you will be in the gdates hall of fame if you manage to do it

mjobuda commented 3 years ago

It's a contest in gitcoin, so anybody can work on it without my permission. But currently you are the only one interested, so go for it!

jbrainz commented 3 years ago

is there a documentation to this, do you have something similar that i can work with ?

mjobuda commented 3 years ago

This Software consists of two pieces. One is the Ghost cms. This is a very popular piece if Software and has documentation. The backend is in emberjs which has also documentation. The other piece is the chat software. This is totaljs messenger based on a framework called totaljs. It's not so popular and has not so much documentation. But it's author is very friendly and answers and questions. Ghost and messenger have their own login page. The login mechanism in ghost is superior. Currently you login to the Ghost cms and a JavaScript call sends the login data and password to the messenger site in a very primitive way. That does not work so well. You are asked usually a second time to login at the messenger site. Emberjs has it's way to login once and use this authentification for other apps. At least I understood it this way! So you'd have to read the emberjs authentication docs (called ember simple auth, but I think it's not that simple :) check their site) and make sure that these credentials are then used by messenger

Pius John notifications@github.com schrieb am Sa., 26. Sep. 2020, 22:41:

is there a documentation to this, do you have something similar that i can work with ?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/mjobuda/gdates-gitcoin-proxy/issues/5#issuecomment-699545659, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADK23JIYBULCGK2JORMEGDDSHZGXTANCNFSM4QPIZCXQ .

jbrainz commented 3 years ago

so its just the code solution that is needed?

mjobuda commented 3 years ago

What do you mean? We need a solution that works, yes. You have to implement it and make sure that it works

Pius John notifications@github.com schrieb am Sa., 26. Sep. 2020, 23:16:

so its just the code solution that is needed?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/mjobuda/gdates-gitcoin-proxy/issues/5#issuecomment-699548878, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADK23JOMBSHIHTRHH4DOIA3SHZK2HANCNFSM4QPIZCXQ .

jbrainz commented 3 years ago

ok

Rashmi-278 commented 3 years ago

Hello , it seems to be still open , can I work on this ?

jbrainz commented 3 years ago

yes you can work on it.

mjobuda commented 3 years ago

Hello , it seems to be still open , can I work on this ?

yes, there is also a bounty on this: https://gitcoin.co/issue/mjobuda/gdates-gitcoin-proxy/5/100023595

Do you have forked the project on gitLAB ? https://gitlab.com/owsikowski/gdates there's where the development takes place.

Are you able to build and run it? I'm still working on proper CI pipelining and it got a little messy

mjobuda commented 3 years ago

i also don't insist that ember auth is used to solve the problem. A short description of the problem: there is a docker container running a hacked version of ghost cms another container runs a chat app. The desired behaviour is that you login once to ghost cms and are logged automatically also in the chat. This works (but it does not work satisfactionary). the first two times the user is also asked by the chat app to login. It should all work flawless(but a quick and dirty workaround is OK with me).