Items to prepare
Last updated
Was this helpful?
Last updated
Was this helpful?
To perform an integration in an external application, the concepts explained in the , , , and sections must be taken into account. All of this management can be done manually, for integrations that do not require automating changes or access, or that do not require giving access to a user in real time.
The automation of all these tasks can be done using the Biuwer public API, which requires coding in your application, to implement the required calls (user management, authentication tokens and data policies, mainly).
It is necessary to take into account how your application is managed at a security level, and consider how your end users need to access the content (Shared Resources), and what data access needs they have, which will determine how many Users Basics must be managed and in what way.
Typically for a multi-tenant B2B application, you must have a dynamic table, normally managed in a database, with the list of Biuwer Authentication Tokens that are associated with each user identifier in your application, which can be user IDs, Company IDs or a combination of both. This mapping table can be called, for example, "integration_security_mapping".
Example of a 1 to 1 mapping table, for 1 Basic User for every 1 end user in your application (assuming a "users" table with a "user_id" field as identifier):
65423600
4656e978-be1f-4b26-96d1-b6215bfc7e87
72471109
baedaa5a-9615-4fbd-9970-0a25bf5b0c88
91660724
961a45a2-a782-4f94-b42b-7506a58c6a5d
88091477
1dc78c2a-dca6-4e92-8db0-d5ae7ace2ad1
Example of 1 to N mapping table, for 1 Basic User shared by multiple (N) end users in your application. This means that different end users in your application will be able to access the same content and data in Biuwer.
65423600
baedaa5a-9615-4fbd-9970-0a25bf5b0c88
72471109
baedaa5a-9615-4fbd-9970-0a25bf5b0c88
91660724
961a45a2-a782-4f94-b42b-7506a58c6a5d
88091477
961a45a2-a782-4f94-b42b-7506a58c6a5d