Implemented user role identification (Member vs Admin vs Guest) for Google Oauth.
I did this using a format very similar to the one seen in Lab07. Now, the administrators are given in the application.properties file under app.admin.emails. Admins are identified by matching their emails to an email in this list.
Members are identified using the UCSB hosted-domain value "ucsb.edu". All users who sign in with an email that doesn't end in ucsb.edu are Guests.
Guests cannot access the Scheduler page. For now, I return a 403 Forbidden Error. (I think the next issue should be to implement an error page for this event.)
Implemented user role identification (Member vs Admin vs Guest) for Google Oauth.
I did this using a format very similar to the one seen in Lab07. Now, the administrators are given in the application.properties file under app.admin.emails. Admins are identified by matching their emails to an email in this list.
Members are identified using the UCSB hosted-domain value "ucsb.edu". All users who sign in with an email that doesn't end in ucsb.edu are Guests.
Guests cannot access the Scheduler page. For now, I return a 403 Forbidden Error. (I think the next issue should be to implement an error page for this event.)