- 4 minutes to read

Permission Set for Log Views

The following permissions exist for the Log Views permission set:

graph LR subgraph "fal:fa-hdd Permissions for Log Views" ro23[fal:fa-lock Permission Set] --> ro1(fal:fa-door-open Global setting) subgraph "Log View" ro2(fal:fa-search Access Log) ro3[fal:fa-key View Context] ro4[fal:fa-download View Body] ro5[fal:fa-file-alt View Transformed] ro6[fal:fa-repeat Resend] ro7[fal:fa-magic Repair] end ro1 --- |Allow or Deny| ro2 ro1 -.- |Inherit, Allow or Deny|ro3 ro1 -.- |Inherit, Allow or Deny|ro4 ro1 -.- |Inherit, Allow or Deny|ro5 ro1 -.- |Inherit, Allow or Deny|ro6 ro1 -.- |Inherit, Allow or Deny|ro7 end

Access Log

To access the Nodinite Log Views; The User must be a member of a Role granted (Allow) access to the Log.

NOTE: If the User is a member of any Role where access to the Log is denied (Deny); Then the user is blocked access to ALL Log Views.

Access right

  1. The Role is set to Allow access to the Log.
  2. The Role is set to have different access rights to individual Log Views.
    • Allow - Log View is visible and accessible to the end-user.
    • Deny - Log View is NOT visible or accessible to the end-user.

View Context

In the Log Views, for end-users in Roles where the View Context permission is allowed; The end-user is granted the right to view the Context Values tab.
Context Values tab
Example of the Context Values tab as seen in a Log View

  • Inherited - Context data is visible and accessible to the end-user IF the global setting is set with the Allow option; Otherwise, it is not.
  • Allow - Context data is visible and accessible to the end-user.
  • Deny - Context data is NOT visible or accessible to the end-user.

To further protect sensitive Context data, Nodinite can mask the values presented to end-users. Review the ProtectedContextValues user guide for details.

View Body

In the Log Views, for end-users in Roles where the View Body permission is allowed; The end-user is granted the right to view the Body.
Body
Example of the View message Body Action menu item on a selected Log Event as seen in a Log View

With this grant, end-users can Download the body/payload. There are different download options (single, multiple, ...) available in various places within the Web Client.
Download Action
Single download example

  • Inherited - The Body (RAW data) is visible, accessible and downloadable to the end-user IF the global setting is set with the Allow option; Otherwise, it is not.
  • Allow - Log View is visible, accessible and downloadable to the end-user.
  • Deny - Log View is NOT visible, accessible or downloadable to the end-user.

View Transformed

Nodinite has a feature built-in to render the payload (Body) in other presentation formats using a Stylesheet. This feature helps your business better grasp the content of message transactions. Also, use it to filter/mask sensitive data.

  • Inherited - Transformation option is available to the end-user IF the global setting is set to Allow; Otherwise, it is not.
  • Allow - Transformation option is available to the end-user.
  • Deny - The transformation option is NOT available to the end-user.

Resend

In the Log Views, for end-users in Roles where the Resend permission is allowed; The end-user is granted the right to resend the Body.
Resend
Example of the Resend Action menu item on a selected Log Event as seen in a Log View

With this grant, end-users can Resend the body/payload. There are different resend options (single, multiple, ...) available in various places within the Web Client.

  • Inherited - The Resend feature is available to the end-user IF the global setting is set with the Allow option; Otherwise, it is not.
  • Allow - Log View is visible, accessible and downloadable to the end-user.
  • Deny - Log View is NOT visible, accessible or downloadable to the end-user.

NOTE: The AllowResubmit System Parameter must be set to true; Otherwise, the Resend feature is disabled.

Repair

In the Log Views, for end-users in Roles where the Resend and Repair permissions are allowed; The end-user is granted the right to Repair the Body.

Repairing and resending messages is an advanced feature. To Repair a Log Event; First, click on the View Details menu Action.
View Details
View details Action button menu item

This opens another tab in the Client Browser with a new page. On this page, you can then click on the Repair and resubmit menu button.
Repair and resubmit menu button

Repair
Example of the Repair and Resubmit modal for selected Log Event

With this grant, end-users can Repair and Resubmit the body/payload using the Web Client.

  • Inherited - The Repair and Resubmit feature is available to the end-user IF the global setting is set with the Allow option; Otherwise, it is not.
  • Allow - The Repair and Resubmit feature is visible and accessible to the end-user.
  • Deny - The Repair and Resubmit feature is NOT visible or accessible to the end-user.

The AllowResubmit and the AllowRepair System Parameter must both be set to true; Otherwise, the Repair and Resubmit feature is disabled. Also, the Resend permission must be set to Allow.


Next Step

Add or manage Role
Add or manage Log View
Add or manage Monitor View
Repository Model

Users
Log Views
Monitor Views
Access Management