DOCSEARCHbyAlgolia
Submit Docs

Nodefusion Account User Manual

website·Indexed 32 days ago

https://account-manual.nodefusion.com

Documentation for Nodefusion Account, covering tenant administration, user list management, application configuration, and Single Sign-On (SSO) integration with Microsoft Entra.

Tokens
1.4K
Snippets
3
Records
13
Agent score
50%

What's inside Nodefusion Account

  1. Access Nodefusion Account and associated applications

    The primary entry point for Nodefusion Account is login.nodefusion.com. The following applications utilize Nodefusion Account for authentication:

    • Aexum: app.aexum.com
    • Aexum Preview: app-preview.aexum.com

  2. Manage Provisioned Users via Microsoft Entra Security Groups

    To control which users are synced to Nodefusion Account, use a dedicated security group:

    1. Create Security Group: In Microsoft Entra Groups, create a new Security group named NodefusionAccount-SCIM-Users and add the desired users.
    2. Assign Group to App: In the Nodefusion Account SCIM Enterprise Application, go to Users and groups -> + Add user/group and assign the NodefusionAccount-SCIM-Users group.

    Only members of this specific group will be provisioned. Adding or removing users from this group manages their access to Nodefusion Account.

  3. Configure Microsoft Entra SSO for Nodefusion Account

    To enable Single Sign-On (SSO) via Microsoft Entra, add the Nodefusion Account to your Microsoft Entra Enterprise Applications. This can be initiated by having a Tenant Administrator register on the Nodefusion Account login page, which should trigger a registration prompt. Once added, define the specific users and groups allowed to access the application within the Nodefusion Account Enterprise Application settings.
    Login URL: https://login.nodefusion.com/```

  4. Assign or remove Tenant Administrator rights

    Tenant Administrator rights can be granted or revoked by toggling the 'Tenant Administrator' checkbox in the user's details page and clicking Save.

    Constraints:

    • To prevent tenant lockout, if a user is the only active tenant administrator, the administrator fields are disabled and the Save button is hidden.
    • SCIM synchronization does not affect Tenant Administration access rights.

  5. View enabled applications in Nodefusion Account

    Tenant Administrators can view the list of applications associated with their tenant by navigating to the Tenant administration portal. The application list displays the Application name, its Enabled status, and available Actions. Note that this list is read-only; applications cannot be enabled or disabled directly from this page.
    Navigate to: https://login.nodefusion.com/Tenant/Apps -> Applications

  6. Activate or deactivate a Nodefusion Account user

    Users can be activated or deactivated by toggling the 'Enabled' checkbox in their user details and clicking the Save button. A deactivated user is unable to log into the Nodefusion Account portal or any application that utilizes it as a Login Provider.

    Caveat: If SCIM is configured and the user is within the sync scope, the 'Enabled' status will be synchronized from the SCIM provider, and manual changes made in the portal may be overwritten.

  7. Configure Microsoft Entra for SCIM Provisioning

    Set up the SCIM connection in Microsoft Entra to automate user provisioning to Nodefusion Account:

    1. Create Application: In Microsoft Entra Enterprise Applications, select + New Application -> Create your own application. Name it Nodefusion Account SCIM and select Integrate any other application you don't find in the gallery (Non-gallery).
    2. Provisioning Settings: Under the application's Provisioning section:
      • Set Provisioning Mode to Automatic.
      • Set Tenant URL to https://login.nodefusion.com/scim/v2.
      • Paste the generated APIKey into the Secret Token field.
      • Click Test Connection, then Save.
    3. Configure Mappings:
      • Disable provisioning of Entra ID Groups.
      • Edit User mappings: Set externalId as the matching attribute and map it to the objectId source attribute. Delete all other mappings except the five primary required mappings.
    Tenant URL: https://login.nodefusion.com/scim/v2

  8. Manage and view Tenant Users in Nodefusion Account

    To manage tenant users, a Tenant Administrator must navigate to the Tenant administration section of the Nodefusion Account portal. The Users menu provides a list of all tenant users, displaying their Display Name, Email, Username, and Enabled status. Clicking on a user's Display Name opens a detailed view containing the user's Id, DisplayName, Email, Username, Enabled status, and TenantAdmin status.

  9. Enable SCIM User Provisioning in Nodefusion Account

    Before configuring the identity provider, you must generate a SCIM API key within the Nodefusion Account portal:

    1. Ensure you have the Tenant Admin permission role.
    2. Navigate to the Manage your Tenant link in Nodefusion Account.
    3. In the left menu, go to SCIM and click Create New.
    4. Select Microsoft as the login provider and add optional internal notes.
    5. Click Create and copy the Generated APIKey for use in Microsoft Entra.

  11. Manually provision or update users for a tenant application

    For applications that are enabled, administrators can trigger two background processes to synchronize user data:

    1. Provision Users: Initiates the creation of all tenant users in the selected application.
    2. Update Users: Triggers an update of existing user data for all tenant users in the selected application.

    Both actions are processed asynchronously in the background and may take several minutes depending on the user count. If SCIM is already configured and functional, Nodefusion Account handles create/update operations automatically, making these manual actions optional.

  12. Understand the retry schedule for application provisioning actions

    Provisioning and update actions are processed asynchronously. If a request fails, the system automatically retries the operation up to 10 times without requiring user intervention. The retry intervals are: 2m, 5m, 10m, 20m, 30m, 12h, and 24h (the 24h interval is repeated 4 times).