User management for speakers

[ivannov]

As a speakers, I have to first log in before I am able to submit my talk(s), so that I am able to review and edit my bio, as well as my current submissions.

After logging in, speakers should be able to edit their profile, look at the submissions they have for the upcoming conference and their status. The submissions themselves should be editable as well.

Besides the system registration and login, support for Google, Facebook, Twitter and Github should be added.

[BDinevv]

Hello everybody, can I work on this?

[martinfmi]

@BDinevv sure, go ahead

[BDinevv]

Hi! I have most of the functionality working right now. Would anybody like to take a look, or should I directly make a PR when I refactor the code?

Furthermore, I have used Keycloak for authorization and authentication, so that the application is more secure and this way the project can be relieved from the duty of managing authorization and authentication. Is this ok?

[ivannov]

Generally, introducing keycloak or another identity provider is a very good practice.

However, in our case maintaining an additional deployment is an overkill for us (we are doing this conference pro bono and in our spare time). So I would suggest that we keep our current auth model as is

[BDinevv]

Oh, okay. I will rework the solution and come back to you.