To support generation of links to share between the internal (administrative) and external (participant) application, we decided to design it as follows.
...
To ensure that links are not regenerated and stored in the database multiple time we will implement functionality to generate hash codes for each link so it can be compared on regeneration and reused.
The hash code is the key that will be part of the link url ex.
https://<url to external web>/teamlink?id=<HashValue from DB>
https://<url to external web>/tasklink?id=<HashValue from DB>
https://<url to external web>/overviewlink?id=<HashValue from DB>
It will be parsed in the external application and in the external application there should always be shown a minimum amount of information on a unprotected route..
Three routes will be available
...
A details page for each type is in an unprotected route in the external web.
...