You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients are authorization endpoints that will accept user credentials, query the server for the authorization response, unlock the resource if appropriate, and deliver feedback to the user.
Different clients may have different available features, so this needs to be taken into account. The current system uses plugins for each distinct feature (card reader, door unlocker, chime, etc.) and the relevant features are selected when setting up the client. Another option would be to have the client report what modules it has installed and have the server assign them automatically.
For the initial implementation we need a way to add new clients and view/edit/remove existing clients.
Clients are authorization endpoints that will accept user credentials, query the server for the authorization response, unlock the resource if appropriate, and deliver feedback to the user.
Different clients may have different available features, so this needs to be taken into account. The current system uses plugins for each distinct feature (card reader, door unlocker, chime, etc.) and the relevant features are selected when setting up the client. Another option would be to have the client report what modules it has installed and have the server assign them automatically.
For the initial implementation we need a way to add new clients and view/edit/remove existing clients.
Current database schema can be viewed here for reference: https://github.com/MakeICT/electronic-door/blob/master/server/software/schema.sql
The text was updated successfully, but these errors were encountered: