Share
Report MPOS activation
You’re offline. This is a read only version of the page.
10
The warning about failed attempt validating the token lists relying parties registered for your issuer, do you see there in the log the values you provided in HQ? Do you also see the issuer value? Can you closely compare the incoming values seen in the log with those actually present in the DB and printed in the log?
I assume you executed the job 1110 and made sure it completed successfully. You can confirm whether the changes you made in HQ were really synced to your channel DB by analyzing the tables:
ax.RETAILIDENTITYPROVIDER
ax.RETAILRELYINGPARTY
ax.RETAILSERVERRESOURCE
Hi Sergey,
we have done this setup and confirmed it by reviewing. we have create a new relying party with new customized MPOS application(client) id and given the redirect URI in server Resource Id.
The warning seen in the very first screenshot, the one saying about Relying Party, describes the reason of the error you are seeing in MPOS, to address it you need to setup HQ with Identity related information so Retail Server would accept the incoming security token, please see more details in Enable newly created AAD applications on AX side
Hi
Thank you for the reply.
these are the logs found in retail server.
i have an app registration with this application id in azure portal, i am not sure is there any step i am missing
Based on the information you provided I can see you looked into MPOS log, but you need to look into Retail Server log to find out exact reason for the misconfiguration.
i face same issue file activating MPOS with customization. this is one warning i have in event viewer :
1. AzureActiveDirectoryUserAuthenticationProvider.acquireTokenWithParam skipped accessing current user's information because corresponding data structure was not initialized.
2. DeviceAuthenticationProvider.acquireToken did not find a device token in the application stroage.
3. Server response status code is '401'.
4. Unauthorized response with error: The audience validation failed.. ErrorResourceId: Microsoft_Dynamics_Commerce_Runtime_InvalidAudience with Correlation Id:
5. The Retail Server Request with request id '-------------' and request url '--------------/Commerce/ActivateDevice?api-version=7.3' failed. Error: The audience validation failed., Status code 401.
6.Chained request execution failed.
7.Device Activation failed. Errors=[{"errorCode":"Microsoft_Dynamics_Commerce_Runtime_InvalidAudience","message":"The audience validation failed. Contact your system administrator to set up identity providers properly in retail headquarters.\r\n- If you are using Personnel ID and Password logon, make sure relying parties are correctly configured.\r\n- If you are using Azure AD logon, make sure both relying parties and server resource ids are correctly configured."}];
(Made sure AADClientId and AADRetailServerResourceId in DllHost.exe file is same as in the HQ parameter relying party and server resource id. )
8. The device activation operation failed.
Please look into Retail Server's log, it will contain a warning with very detailed description on why exactly this fails and how to fix that.
Hi Chi-chi,
Try to check your Identity Providers in Retail > HQ setup > Retail Shared Parameters by select the sts.windows.net/<guid>.
In the Relying Party Fast Tab section, you can to check if you have input a valid AppID to it. If not, insert a correct value and run the 1110 job to push the data down to the store and try to activate your MPOS again.
If the issue still persists, please open a new support incident to report it and we will investigate it further for you.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (
