Currently administrators must manually post username and password to a token endpoint in the veda-backend ingest api and copy paste the token from the response for workflows operations. Update this auth flow to follow the more standard redirect to auth provider for a secure username and password form entry and redirect to the swagger docs.
AC
[x] token auth urls are configurable by veda environment
[ ] cognito user pool updated to allow callback to veda data airflow workflows api docs
[x] admins in the cognito user pool associated with backend stack can login via swagger docs
[x] admins can successfully use authenticated endpoints like collections/ and ingestions/
[x] attempted authenticated airflow pipelines triggers like discover-items and documented success or error response (there are networking issues that may block successful discovery pipelines that should not block the success of this issue)
cognito user pool updated to allow callback to veda data airflow workflows api docs
since we decided it would be easier for an admin to add the callback url manually via AWS console
What
Currently administrators must manually post username and password to a token endpoint in the veda-backend ingest api and copy paste the token from the response for workflows operations. Update this auth flow to follow the more standard redirect to auth provider for a secure username and password form entry and redirect to the swagger docs.
AC