In the PR, we're introudcing improvements to the postgres server by allowing for applications to be connected to owners through a separate table, supporting affiliations, and improving controls through enforcing uniqueness for ids and api keys. api keys and are now generated in psql instead of the application itself.
Also, we cleaned up the Db service to decouple api_key creation and uniqueness checks from the application. Through leveraging the postgres server, we minimize the amount of time it would take to generate a new application.
In SAML land, we now accept the idpURL as an environment variable instead of a hardcoded value. Although our main focus in Elon, Elon could change their IDP url, something that would necessitate a PR to change. Now, in case that happens, we would be able to easily update an environ variable and be back in sync.
In the PR, we're introudcing improvements to the postgres server by allowing for applications to be connected to owners through a separate table, supporting affiliations, and improving controls through enforcing uniqueness for ids and api keys. api keys and are now generated in psql instead of the application itself.
Also, we cleaned up the Db service to decouple api_key creation and uniqueness checks from the application. Through leveraging the postgres server, we minimize the amount of time it would take to generate a new application.
In SAML land, we now accept the idpURL as an environment variable instead of a hardcoded value. Although our main focus in Elon, Elon could change their IDP url, something that would necessitate a PR to change. Now, in case that happens, we would be able to easily update an environ variable and be back in sync.