1E Solutions core configuration
The following sections walk through the core settings for 1E Solutions and does not cover solution specific settings. You can reach this page from Solutions Settings > Configuration from each Solution.
For information about details about adding and removing users, setup roles, etc. refer to Application User Management.
Persona Management
Persona management is used to define the persona types in your environment.
-
Initial setup for 1E Solutions creates the Department Persona Type with Other in it. All the users get added to Other by default.
-
Admins can create other persona types and add rules to categorize users into different personas.
-
Whenever a rule is created, admins need to run the rules by clicking RUN RULES. After the rules are successfully evaluated, admins will see the list of users under the Members tab.
There is no auto run set for persona rules, so you should run rules as required.
API Management
The API Management section is used for configuring the following API functions.
1E Platform
You will need to complete these fields.
|
Field |
Description |
|---|---|
|
1E Platform FQDN |
<name of your 1E instance>. |
|
OAuth token issuer application ID (Client Assertion ID) |
Application (Client Id) of the 1E Integration AAD application. |
|
Certificate Password |
The certificate password for the non-interactive login. |
|
KID |
The KeyID (KID) of the certificate. |
|
Private Key |
Paste a copy of your Private Key, and ensure that only the Private Key component from the PEM file is used here. |
|
Platform Sync account |
Used to authenticate the background jobs running on Solutions. |
|
Enable Management Group Sync |
Syncs the management groups from 1E Platform into Solutions module. |
|
Enable Outbound APIs |
Enables the export of Solutions data. |
|
Auth Token |
The authentication token is required to authenticate requests to the Solutions export APIs. This field is activated when you select Enable Outbound APIs. |
When you have completed the form, click Save.
The following controls are used for:
-
Setup 1E Platform: Creates event subscriptions, notifies you if there is a mismatch of the 1E Solutions Core DEX Pack, checks your license, creates event subscriptions, and updates your Solutions menu to match your currently licensed Solutions.
-
Check Event Subscription: This is required for 1E Device Refresh. Displays any existing event subscriptions. If there are none, clicking Reset Event Subscriptions will automatically create them.
-
Sync Now: Initiates the device sync and management group sync.
Email Configuration
Use Email Configuration to send emails to end-users and your service desk based on Solution Actions. 1E Solutions use Microsoft Graph API to send emails, refer to Azure authentication setup for the permissions required.
|
Field |
Description |
|---|---|
|
Sender Email Id |
This email is used for sending emails to users. This should be a valid email id and should have an inbox. |
|
ServiceDesk Email Id |
This is the email id of the Service desk to which emails will be sent. |
|
Email Subject |
Subject of the email. You can include <DeviceSolutionStatus>; and <DeviceName>; in the subject line. <DeviceSolutionStatus>; and <DeviceName>; will be replaced by the actual values. |
|
Email Body |
This will be the body of the email. You can include <DeviceSolutionStatus>; and <DeviceName>; in the subject line. <DeviceSolutionStatus>; and <DeviceName>; will be replaced by the actual values. |
|
Email Signature |
This is used to include the signature of the email. |
When you have completed the form, click Save.
Emails will now be sent based on your Solution Actions rules.
Third Party Configuration
Third Party Configuration is used to set up integrations between 1E Solutions and third-party systems. These configurations enable 1E to open incidents for Device Refresh based on solution actions. 1E Solutions supports ServiceNow and Jira Service Management.
When the following parameters are included in the body, they are replaced by the accompanying value.
-
<RuleName>: Actual rule name that triggered the instruction.
-
<DeviceName>: Actual device name on which rule has failed.
-
<UserName>: Primary user of the device.
-
<UserEmail>: Email of the primary user.
ServiceNow example:
Jira Service Management Example:
Run Import Device API
Run Import Device API is used to push pending device information from the staging table to the main device table. Because there is a scheduled job to automatically push the devices, it is recommended this function should only be used if there is a need to immediately push them to the main table (for testing/troubleshooting).
View Audit Log
Audit logs offer a comprehensive record of all admin and device activities, including event-related data. Customers can access detailed logs to track changes. Audit logs are currently retained indefinitely, ensuring a complete and enduring record of activities.
