How do all three options for generating "Url for access ..." differ

Url for the direct acces

The function returns a URL to the user which contains the repository id, diagram guid and an access key. Using this URL, it is possible (for anyone who knows it) to display the diagram in the Infoport program in the same way the diagram would be seen by the author of the link. The key contained in the URL is actually an authorization token and replaces the need to log in to Infoport.

http://localhost/Repository?guid={3FA89587-2763-4c14-9C98-D3A4E8D741AB}&key={97f018a0-9a87-43b3-b2dd-7ea630b12f64}&repositoryId=4

• The function does not write to any directory and does not subsequently need any file on disk
• It writes to a table (and then subsequently uses it)
  • detail_authorize_key

Url for public diagram

It is used to publish the diagram so that it is accessible to anyone who knows the generated URL. It is a direct link to the directory with diagram images. It is not access to Infoport as such, but only to the directory with generated diagrams.

http://localhost/access/4/3FA89587-2763-4c14-9C98-D3A4E8D741AB.png

• The function writes to directories (and then it also needs to display diagrams from the first one mentioned)
  • /wwwroot/access/[repoid]/
  • /wwwroot/archive/[repoid]/

Whereas /archive/ is not essential for functionality

It also writes to a database table. This table is subsequently needed to verify whether this diagram is really public and accessible to everyone. This check prevents the possibility of displaying the diagram just by knowing its guid (and constructing your own URL)

• detail_diagram_key

Image for the direct access

The function combines the previous two, allowing public access to the diagram image (file from disk), with the option to click through to Infoport and display the diagram and its associated information. This click-through is bound to a valid key. The reason for implementing this function is the requirement to display a "preview" of the diagram (which is sufficient in many cases) but with the option to click through to the Infoport environment for further details and information.

• The function writes to the same directories as the second function
  • /wwwroot/access/[repoid]/
  • /wwwroot/archive/[repoid]/
• and to both tables used by the previous functions
  • detail_authorize_key
  • detail_diagram_key