Solved Salesforce Authorization Redirect Errror

[cmcleman]

Hey,

I'm having trouble getting Saleforce to authorize in 3CX.

As per another forum post suggestion I came across, I've updated the template to include 'test.salesforce.com' in the template where it's referenced a few times, as the customers Salesforce is currently in sandbox.

Url="https://test.salesforce.com/services/oauth2/token"

On attempting to authorize, it returns the below error code:

{"state":["The state field is required."]}

Has anybody come across this before and found a resolution?

Many thanks,

 

[Charles_3CX]

The error in the log that you receive will have the field that needs to be visible. For example, it is related to the HomePhone field on the Contact entity. However, this error might also occur for other fields or entities, which you may check in the 3cxsystemservcie.log within the support info in verbose after replicating the issue.

To fix this, the customer needs to make visible the field in Salesforce as follows (for the fields related to the issue):
- Go to “Setup Home > Objects and Fields > Object Manager > Contact > Fields.”
- Click on the field you want to make visible, for example, “HomePhone”.
- Press the “View Field Accessibility” button on the upper right side of the screen.
- Click on the “Hidden” label on the right of “Standard User” (or the profile of the user configured for the integration).
- Under the “Field-Level Security”, check the “Visible” option.
- Repeat the procedure for other fields or entities, causing the same error.

 

[Evolute IT]

Hey,

I'm having trouble getting Saleforce to authorize in 3CX.

As per another forum post suggestion I came across, I've updated the template to include 'test.salesforce.com' in the template where it's referenced a few times, as the customers Salesforce is currently in sandbox.

Url="https://test.salesforce.com/services/oauth2/token"

On attempting to authorize, it returns the below error code:

{"state":["The state field is required."]}

Has anybody come across this before and found a resolution?

Many thanks,

It's one of the oauth settings in Salesforce I think. Review the full config doc to make sure you didn't check/uncheck a wrong box.

 

[TheodorosG_3CX]

Ensure that the steps 6-10 are followed exactly as this is related to specific options and scopes assigned in Salesforce:
• https://www.3cx.com/docs/salesforce-crm-integration/

 

[cmcleman]

It's one of the oauth settings in Salesforce I think. Review the full config doc to make sure you didn't check/uncheck a wrong box.

It looks like some of the settings reverted within OAuth section of the Salesforce App module.

"Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows" and "Require Secret for Refresh Token Flow" options had reverted to enabled.

After unticking these and re-saving, it stopped the MFA challenge and authorized straight away.

Thank you.