Several of our interns have written addons that require the user to authorize OSF access to their private resources via OAuth. We are using a wrapper to make OAuth easier, but there are some non-obvious stumbling blocks.
Per @KushG, it isn't obvious how state tokens (nonces) are used to connect the initial callback from the service to the user or node who initiated the request. We could likely wrap this functionality to make it even easier.
Several of our interns have written addons that require the user to authorize OSF access to their private resources via OAuth. We are using a wrapper to make OAuth easier, but there are some non-obvious stumbling blocks.
Per @KushG, it isn't obvious how state tokens (nonces) are used to connect the initial callback from the service to the user or node who initiated the request. We could likely wrap this functionality to make it even easier.