Is your feature request related to a problem? If so, please describe.
No.
What is your new feature idea or request?
In preparation for ULSv3, new endpoints to be setup that allow management of the soon to exist OAuth Client table. Facilities need a Client ID (either randomly generated or we can use their Facility ID), and allow dynamic creation of Client Secrets. We also need to allow editing of the Redirect URI field, which is just storage of a JSON array of strings that contain URIs that will be validated by ULSv3.
Contact Details
daniel@hawton.org
Is your feature request related to a problem? If so, please describe.
No.
What is your new feature idea or request?
In preparation for ULSv3, new endpoints to be setup that allow management of the soon to exist OAuth Client table. Facilities need a Client ID (either randomly generated or we can use their Facility ID), and allow dynamic creation of Client Secrets. We also need to allow editing of the Redirect URI field, which is just storage of a JSON array of strings that contain URIs that will be validated by ULSv3.
Model: https://github.com/VATUSA/uls/blob/dev/database/models/oauthclient.go
Note: we no longer need to generate a JWK for each facility, each token will be signed using a VATUSA JWK KeySet with public keys available for validation (https://github.com/VATUSA/uls/blob/dev/controllers/v1/certs.go).