You need to sign in to do that
Don't have an account?
PFL Administrator
Canvas App Winter 16 issue
We have a Canvas connected app that is using the Web Server OAuth flow. This is working for all of our clients except for one who is in version winter 16 beta and Performance Edition in their sandbox. We have “Admin approved users are pre-authorized”. However for this client we are getting an error from the RemoteAccessAuthorizationPage.apexp (see the ConsoleLog.png), it is refusing to display because of the x-frame-options. It is our understanding that with the pre-authorized OAuth setting, this page does not need to display, but simply redirect back to our Canvas app. If we open the RemoteAccessAuthorizationPage in another window (outside the iframe), we see the see the page in the attached RequestingPermission.png image. We are presuming this is the page users would see if the OAuth setting was “All users may self-authorize”. After clickin “allow” on this page, our Canvas app authorizes and loads. We want to help this customer use our app. Can you tell us why this is not working and how to fix it? Is there an additional setting needs to be tweak for this version?
A second issue is that the request to our Canvas app from all installed instances comes from a URL host ending with “visual.force.com”. From this customer the URL host is “cvent--pcopy.cs21.my.salesforce.com” which does not end with “visual.force.com”. Why is that?
A second issue is that the request to our Canvas app from all installed instances comes from a URL host ending with “visual.force.com”. From this customer the URL host is “cvent--pcopy.cs21.my.salesforce.com” which does not end with “visual.force.com”. Why is that?
See: https://help.salesforce.com/apex/HTViewHelpDoc?id=domain_name_app_url_changes.htm&language=en_US
http://salesforce.stackexchange.com/questions/91586/oauth-from-vf-page-in-new-lightning-cannot-redirect-vf-page-to-login-salesforc
PFL Administrator,
You mention in the original post "we have “Admin approved users are pre-authorized”". This setting is a per org option. So, when your customers install the app, they have to make sure that they have approved the app for their users. This is not new to the Winter 16 release.
The behavior you describe happens when the app is not pre approved. In this case, since you have set the access method as OAuth, it is up to your app to manage the flow. Part of the management is that you do not try to embed the autorization page in an iframe where it will be blocked. Instead, you would have to use a pop-up display as is outlined in the canvas docs.
Hope this helps.
Jay