-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User management for speakers #120
Comments
Hello everybody, can I work on this? |
@BDinevv sure, go ahead |
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? |
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 |
Oh, okay. I will rework the solution and come back to you. |
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.
The text was updated successfully, but these errors were encountered: