Enforce Authentication for WPS-T ADES front-end and TEP back-end

unity-sds / unity-sps-prototype

Apache License 2.0

2 stars 7 forks source link

Enforce Authentication for WPS-T ADES front-end and TEP back-end #60

Open LucaCinquini opened 2 years ago

LucaCinquini commented 2 years ago

Acceptance Criteria

WPS-T endpoint is accessible to logged in memebers of the Unity System
SounderSIPS memebers have been on-boarded into the appropritate Authentication Realm
Users can access WPS-T endpoint by Browser (Human based, interactive Auth)
Users can access WPS-T endpoint by API (e.g. command Line or machine to machine, non-interactive auth)
Users who are not authenticated are redirected to login mechnism"
Deployed to MCP Dev
Deployed to MCP Test

mike-gangl commented 2 years ago

I assume TEP backend is HySDS in this instance, correct? for the prototype, what auth is required and what TEP endpoints are we interacting with from the user perspective?

LucaCinquini commented 2 years ago

Yes TEP back-end is HySDS. That said, we need to discuss wether we want to expose any of the HySDS UIs to the user or not. At the very minimum, the WPS-T interface needs to be secured with authentication. I am not sure if we want and/or have the resources to secure the HySDS UIs. Maybe we don't need them for the prototype.