06 – Authentication Token

Push365 enables you to send interactive notifications to users. These interactions are referred to as Notification Actions.
For more details, please refer to Notification Actions.

In this section, we’ll explain how you can make Notification Actions more secure.

To access Dataverse actions or custom APIs, you need to define a token. These are referred to as Authentication Tokens.

Currently, Push365 supports two types of Authentication Tokens:

• AAD Application User
• Basic Authentication Token

An AAD Application User is an application user definition required to access Dataverse actions (endpoints).
This configuration uses an existing Application User already defined in your system and allows you to execute Dataverse actions through related notifications.

A Basic Authentication Token is used to access public API endpoints using the Basic Authentication mechanism.
If you have any API endpoints that require secure access, you can use this token to authenticate those requests.

An important point to remember is that securely storing, using, and removing these tokens when necessary is your responsibility. Push365 acts only as a carrier for these tokens and does not assume any responsibility for the operations performed on the endpoints accessed using them. To prevent misuse, especially for Dataverse endpoint access, we strongly recommend assigning only the minimum required permissions to the Application Users associated with AAD Application User tokens. Security roles should be limited strictly to what is necessary.

For more information about Dataverse Application Users, please read Microsoft ‘s official documentation https://learn.microsoft.com/en-us/power-platform/admin/manage-application-users

For more details, please watch the following video.

For more content, visit our YouTube channel