Purpose and Introduction for EmbeDash iFrame

EmbeDash provides tenants with access to a sample application or sample code repository portal, enabling them to make necessary adjustments to the code based on the requirements of the EmbeDash application.

Certainly, let me elaborate further:

When EmbeDash is seamlessly integrated into an ISV/Tenant application and the reports are displayed within that application, a user’s interaction with a specific report triggers a process. In this process, the ISV/Tenant application initiates a request to the internal system. This request is crucial as it prompts the internal system to generate a special token, known as a JSON Web Token (JWT).

A JSON Web Token is a secure and compact way to represent claims between two parties. In this case, the tenant, using their private key, generates this token. This token serves as a digital signature, ensuring the authenticity and integrity of the data being transmitted. 

This mechanism ensures a secure and verified user experience, where EmbeDash validates the user’s request and provides access to the requested report within the ISV/Tenant application.

To verify the signature of the JWT token, the ISV shares the public key with EmbeDash. The ISV uploads a file containing the public key during the tenant creation process. The option to upload the public key is available on the create and edit tenant screens for the Super Admin persona. EmbeDash securely stores the public key as an encrypted value.

ISVs can utilize RSA cryptography to generate private-public key pairs.

During token verification, EmbeDash decrypts the encrypted public key and utilizes it to verify the token signature.

In the event of an unsuccessful token verification, EmbeDash denies access. Consequently, the client attempting to access the report will be presented with a message “No Access”.