Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to update some settings in on-premises due to Authentication error #73

Closed
sivakesava6666 opened this issue May 20, 2021 · 3 comments

Comments

@sivakesava6666
Copy link

Settings failing with update:
"UseFilteringMethodOfSyncingMailboxOnlyForCorrelation".
"IgnoreConversationIndexAndInReplyToForCorrelation".
"ResolveForInactiveEntities".

Error details:
image

On-Premises CRM version:
9.0.22.8

@seanmcne
Copy link
Owner

seanmcne commented Jun 2, 2021

The version of your onprem deployment appears to be missing the setting you want to add:
image

You may require an update which contains these settings, I try to do my best to align with the right version #'s but that usually is mostly aligned to Online version numbers as there can be some differences. Support should be able to confirm if the setting is in a given (specific) version of onprem.

@siovchev0
Copy link

siovchev0 commented Jun 3, 2021

Hi Sean,
Thanks for the answer.
Actually, the settings are available on said version. The problem comes only after enabling IFD. The solution expects only kerberos authentication. The same settings could be updated fine if IFD is not set up. Even before enabling claims-based auth.

Fiddler logs show kerberosmixed is called. Disabling the kerberos endpoint did not help.
The solution itself may call the wrong crmservice.

Could you provide your feedback on the above?
Thank you in advance.

*apologies for the font

@seanmcne
Copy link
Owner

seanmcne commented Jun 4, 2021

Thanks for the update! Do you have an example you can share of what this looks like in the UI? It should be accessing the API using the auth context of the user who loaded the page - the exception should be what it is seeing from the HTTP response from the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants