search

nixahams / nixahams-website

Website Code
MIT License
3 stars 1 forks source link

Permission Levels #4

Open proesslet opened 1 year ago

proesslet commented 1 year ago

It would be useful to have permission levels that would allow different pages to be seen by different people.

  1. Standard club member that can log in and have contact info of other club members & be able to view the repeater dashboard showing what repeaters / links are receiving when a person is talking as well as view Allstar node and DV Switch
  2. Control Operator level that can view and control the relay boards, EchoLink and all Star nodes and voter
  3. Admin Level: All of the above plus log in and make configuration changes to all the above equipment - if nothing else via links with passwords and single sign on if that’s possible.

This project will need a combination of some front end and some backend work to make it happen

For a login system, we could continue to use Passport and our own authentication method, or we could look into using Passport with OAuth to allow users to sign in with Google, Facebook, etc as well as protect some of the more sensitive pages with MFA if we feel that is needed

nixahams commented 1 year ago

I like the option of being able to sign in with google or facebook - I use that sometimes when I forget a specific password and that option is available.

James Adkins 417-834-2745 (cell) Amateur Callsign = KB0NHX GMRS Callsign = WROQ478 www.nixahams.net www.smlrs.info

"Raise the standards . . . If the people lead, eventually the leaders will follow"

"Those saying it can't be done should get out of the way of those doing it"

On Fri, Jun 16, 2023 at 5:41 PM 'Preston Roesslet' via k0nxa < @.***> wrote:

It would be useful to have permission levels that would allow different pages to be seen by different people.

  1. Standard club member that can log in and have contact info of other club members & be able to view the repeater dashboard showing what repeaters / links are receiving when a person is talking as well as view Allstar node and DV Switch
  2. Control Operator level that can view and control the relay boards, EchoLink and all Star nodes and voter
  3. Admin Level: All of the above plus log in and make configuration changes to all the above equipment - if nothing else via links with passwords and single sign on if that’s possible.

This project will need a combination of some front end and some backend work to make it happen

For a login system, we could continue to use Passport and our own authentication method, or we could look into using Passport with OAuth to allow users to sign in with Google, Facebook, etc as well as protect some of the more sensitive pages with MFA if we feel that is needed

— Reply to this email directly, view it on GitHub https://github.com/nixahams/nixahams-website/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5RLB6UDZGY2JBAH45SCKE3XLTOKLANCNFSM6AAAAAAZJZU4IM . You are receiving this because you are subscribed to this thread.Message ID: @.***>

proesslet commented 1 year ago

This seems like a good place to start planning user accounts...

So each user will be stored in our database and we will need to specify what information each user has. Right now, this is needed information that I can think of:

Is there any other information that anybody else can think of that might be useful to store?

Thinking further down the road, it might be nice for us to have a relational database. Mongo may actually support this, I'd have to do some research, but I'm thinking for things such as Hamfest tickets and such it might be useful to be able to link that back to a specific user. I'll do some more looking into this and see if Mongo has any support for relational data

My idea here, is that after somebody purchases tickets, we would be able to easily implement a feature for them to go to their profile and see their tickets (as well as a confirmation email). This may may be far beyond what you all are wanting, but it could be cool