Add an endpoint for client apps that will return an external ID and a user object, if the external ID corresponds to a record in the TMP_USER table. This PR includes a migration, so once it's merged run mvn flyway:migrate to apply it to the database.
Once this is merged, the demo client's master branch will work with the master branch of this repository again.
@kfogel and I talked briefly about the security implications for this new endpoint. If a person has the id_token corresponding to a given Google address then they could log in to an HMIS server as that Google address anyway, so we don't think this opens up any additional risk. Do let us know if we're overlooking something.
Add an endpoint for client apps that will return an external ID and a user object, if the external ID corresponds to a record in the
TMP_USER
table. This PR includes a migration, so once it's merged runmvn flyway:migrate
to apply it to the database.Once this is merged, the demo client's master branch will work with the master branch of this repository again.
@kfogel and I talked briefly about the security implications for this new endpoint. If a person has the
id_token
corresponding to a given Google address then they could log in to an HMIS server as that Google address anyway, so we don't think this opens up any additional risk. Do let us know if we're overlooking something.