Shared resources
Using the Biuwer interface, from the content listings, you can share any Collection, Page or Card. This step will generate what is called a "shared resource" that has a unique alphanumeric identifier, the Shared Resource Token, that you must take into account to be able to identify the content correctly.
A shared resource includes a validity period, that is, it is valid from a certain date and time, and you can optionally configure a date and time until which it is valid and can be used. If a user accesses a share outside the validity time range, the content not found screen will be displayed.
The integration of a shared resource in an external application is done by inserting an HTML IFRAME in the application code, which can be written using different technologies and languages, but at the end of the day it must be a web application that speaks HTML , CSS and of course, Javascript.
The IFRAME code follows this pattern:
In the previous code, you can modify the width and height of the IFRAME, taking into account that scrolls (horizontal and/or vertical) will be shown when the content does not fit in the configured size. Something common, if you define in your application a DIV with exact dimensions to embed within content, is that in the IFRAME the dimensions are indicated as 100%. This way it would be: width="100%" and height="100%".
The most important thing is the correct configuration of the value of the "name" attribute of the IFRAME, which includes two alphanumeric codes separated by the character ":".
User Authentication Token: this is the unique alphanumeric code that is generated when creating an Authentication Token associated with a specific user in Biuwer.
Shared Resource Token: this is the unique alphanumeric code that has been generated when sharing the content on Biuwer.
In practice, integrating a resource into an application involves including in its code, associated with a route or menu item, an IFRAME like the previous one, where the Shared Resource Token is whatever you want, but it is fixed for the same resource, and the Authentication Token is that of the Biuwer user with which the user identified within your application is uniquely associated.
Last updated
