Understanding the “Request User ID” Interaction Type and Authentication Error

Naama Aharoni
Naama Aharoni
  • Updated

2025-03-05 13_39_56-Innovation Hub - Work - Microsoft_ Edge.png

The “Request User ID” interaction type in MyWave is used to prompt user authentication at a specific point in a Wave. It ensures that the user is logged in before proceeding with a secured interaction, such as submitting data, making decisions, or accessing sensitive actions.

 

If the user is not authenticated when this interaction is triggered, they will see the following error:

“You must be authenticated to do that.”

 

When to Use “Request User ID”

This interaction type is particularly relevant when:

  • A user starts a Wave without logging in (common in web or mobile use cases)

  • The Wave reaches a point that requires authentication (e.g., viewing secure data, submitting a transaction)

Example:

Think of a user browsing a web-based catalog. They can look at items freely, but must log in to add something to the cart or complete a purchase. This is where “Request User ID” is used — to pause the interaction and request authentication before proceeding.

 

Is This Needed in SAP Business One?

No — this interaction is not typically needed in SAP B1 environments.

SAP Business One users must already be authenticated to access the MyWave UI. Therefore, the system handles login upfront, and this interaction type becomes redundant.

You can use it only for scenarios where a user might access part of a Wave without authentication first.

 

Why You Might See the Error:

“You must be authenticated to do that”

This occurs when:

  • The user session has expired or they are not logged in

  • A valid user ID is not passed from the authentication provider or InfoPlugin

  • The authentication step has been skipped or misconfigured

How to Resolve It:

  1. Confirm the user is logged in before this interaction step

    • Use SSO or front-end login mechanisms

  2. Verify authentication setup in the Wave’s configuration

    • Ensure it’s correctly requesting and processing login

  3. Check user ID source

    • If using an InfoPlugin or integration, make sure it’s passing a valid ID

  4. Test in a secure environment

    • Log in with a valid user and trace the Wave step-by-step

Was this article helpful?

/

Comments

0 comments

Please sign in to leave a comment.