we have a connected app with a clientid and secret that are used to access the API. we are suddenly (after years of working) getting errors on the authorization_code grant. We successfully get an authorization code, but when we try to retrieve the access token, the call fails with an error: {"error":"invalid_grant","error_description":"authentication failure"}

unfortunately this is the only response we get, and have no other visibility into the issue. We are getting this in our production instance, but other customers who integrate with Salesforce through our platform are getting the same error. In other words, it is not isolated to a single org or user account, but all users trying to authorize us to interact with Salesforce.

I am completely at a loss as to where to go for help, so any guidance is appreciated.

I have a Canvas app that is available to add to an Account layout. Prior to 10/20/17, the POSTed SignedRequest included a Record in the Context. Now that Record is available, but is an empty JSON object:
 

"context": {
    "user": {
      ...
    },
    "links": {
     ...
    },
    "application": {
      ...
    },
    "organization": {
      ...
    },
    "environment": {
      ...
      },
      "parameters": {},
      "record": {},
      "version": {
        "season": "WINTER",
        "api": "41.0"
      }
    }
 }

My canvas app lives in a Visualforce page
 

<apex:page standardController="Account">
  <apex:canvasApp applicationName="MyApplication" entityFields="*" height="425px" width="100%" />
</apex:page>

Anybody know why I no longer get any record data?

Hi all. We started noticing a few days ago (10/20/2017) that a couple of Visualforce pages we have that make use of the "apex:canvasApp" component are not working because the option for entityFields="*" does not appear to be working correctly. Can anyone confirm this or know how to work around this? Or if there has been a change to the Salesforce platform to cause this? Documentation on the canvas framework for Version 41.0, Winter '18 show that this should still work.

We have a simple Visualforce page that looks like:
<apex:page standardController="Account">
<apex:canvasApp namespacePrefix="mynamespace" applicationName="MyAppName" maxHeight="infinite" width="100%" entityFields="*" />
</apex:page>
which we then include on the Account layout.

In particular, we are using entityFields="*" so we send all fields on the Account record to us in the canvas request. Unfortunately, the "record" field in the canvas request is empty (context.environment.record == {}). We are able to reproduce this in our developer edition org with another canvas app, and we are able to find a workaround in development by specifying a specific list of fields -- e.g. entityFields="Id,Name,Website". However, this is not okay for our package since (a) we want all fields and (b) changing this would require a new package.

Given what we are seeing, we think this is an issue in the Salesforce platform and do not know how to proceed. Has anyone else seen this issue or know if something has changed in the Salesforce platform that would cause this issue?

Thank you in advance!

Hi all. We started noticing a few days ago (10/20/2017) that a couple of Visualforce pages we have that make use of the "apex:canvasApp" component are not working because the option for entityFields="*" does not appear to be working correctly. Can anyone confirm this or know how to work around this? Or if there has been a change to the Salesforce platform to cause this? Documentation on the canvas framework for Version 41.0, Winter '18 show that this should still work.

We have a simple Visualforce page that looks like:
<apex:page standardController="Account">
<apex:canvasApp namespacePrefix="mynamespace" applicationName="MyAppName" maxHeight="infinite" width="100%" entityFields="*" />
</apex:page>
which we then include on the Account layout.

In particular, we are using entityFields="*" so we send all fields on the Account record to us in the canvas request. Unfortunately, the "record" field in the canvas request is empty (context.environment.record == {}). We are able to reproduce this in our developer edition org with another canvas app, and we are able to find a workaround in development by specifying a specific list of fields -- e.g. entityFields="Id,Name,Website". However, this is not okay for our package since (a) we want all fields and (b) changing this would require a new package.

Given what we are seeing, we think this is an issue in the Salesforce platform and do not know how to proceed. Has anyone else seen this issue or know if something has changed in the Salesforce platform that would cause this issue?

Thank you in advance!