Embeddable View
Last updated
Last updated
Nected introduces a powerful framework for embedding users and providing pre-signed authentication. These features offer seamless integration and secure access control mechanisms, empowering organizations to embed Nected’s UI components and enable direct sign-ins with pre-signed URLs.
Below is the overview on how to generate pre-signed urls to embed rules and workflows within another product.
To integrate Embedded Users Flow with the Embedded View, here's how you can access and manage it for these users:
Navigate to Workspace Settings:
Go to the Workspace section in the Nected platform.
Click on the Embedded Users tab under the Workspace menu.
Add Embedded Users:
Input the email address of the user in the "Add user by email" field.
Assign a role using the Select Role dropdown menu.
Click Add User to grant access.
For each user added, you can provide access to Embedded Views through the pre-signed authentication URL.
Generate the Pre-signed Token using the provided API.
Endpoint: (<https://api.nected.ai/dev/signed-token?email=>)<member-email>
HTTP Method: GET
Authentication Parameters
email
String
Yes
User's email address for token generation
nected-api-key
String
Yes
Organization's unique API authentication key
Access the Postman workspace: Nected Public Workspace. Locate the collection under "Embed Rules and Workflow White-labeling." Utilize provided APIs to fetch UI component configurations
2. Response Structure
When successfully executed, the API returns a comprehensive JSON response containing the pre-signed authentication token:
Nected's pre-signed authentication supports targeted redirections, allowing administrators to guide users directly to specific platform sections:
/rules
Rule Management Interface
/workflow
Workflow Configuration Dashboard
Example Rule Url:
Embed Workflow Example
Embedding via iframe is currently feasible for self-hosted deployments to avoid cross-domain issues. In Saas deployments, custom domains are not present thus preventing option to embedd UI due to cross-domain issue.
The pre-signed authentication API implements a robust error management strategy, providing clear, actionable feedback across various potential failure scenarios:
401
UNAUTHORIZED
Invalid or expired API credentials
Verify API key and regenerate if necessary
500
INTERNAL_SERVER_ERROR
Unexpected system malfunction
Contact Nected technical support
429
TOO_MANY_REQUESTS
Authentication request quota exceeded
Implement exponential backoff strategy
413
REQUEST_ENTITY_TOO_LARGE
Malformed authentication request
Validate request parameters and ensure payload size is within limits
400
BAD_REQUEST
Malformed authentication request
Validate request parameters
Implement strict API key rotation policies
Utilize HTTPS for all API interactions
Generate pre-signed URLs dynamically and close to the point of use
Establish clear access governance policies
Regularly audit user access and permissions
For advanced implementation guidance, architectural consultations, or technical support, please get in touch with Nected's dedicated support team at assist@nected.ai