Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Being a background process that runs unattended, presenting any sort of question to a user (which would be me) isn't really an option.</p> </blockquote> <p>As I already said, you only have to do it <strong>once</strong>.</p> <p>You get your non-expiring page access token, copy&amp;paste that into your app – and from then on your app can do server-side whatever it wants to do happily everafter.</p> <blockquote> <p>I've also been told that I can't do a one-time request from my browser to get an access token because that is, by definition, client-side interaction and not part of the necessary server-side flow.</p> </blockquote> <p>The server-side auth flow for getting a user access token also needs to take part partly in the browser.</p> <p>It does not matter, if you get a short-lived token via the client-side auth flow and extend it afterwards, or if you get a long-lived one using the server-side auth flow.</p> <blockquote> <p>(It seems odd to me that the service would care if a RESTful request comes from a web browser vs. from an application […])</p> </blockquote> <p>Facebook does not want users to give their login credentials to any third party. Therefor, the process of getting a <em>user</em> access token always has to take part in the browser, with the user login in to Facebook.</p> <blockquote> <p>So, if I can perform some manual steps to get a permanent access token for the app to post to the Facebook page, what are those steps? </p> </blockquote> <p>Get a long-lived user access token with manage_pages permission. (Or get a short-lived one, and extend it). And then, use that long-lived token to request a page access token for the target page, in the way that is described in the docs.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload