To start a communication and perform operations on a Joomla! CMS, Joocial requires an OAuth authorization to grant access to the social management action.
The environment where OAuth authorization is performed can be characterized in the following way:
According to this implementation, these are the specific assets where the authorization is generated:
When user initiates a login from the mobile application, these steps are taken to grant the access:
appFactory is the main object that provides the communication services.
appFactory receives the connection parameters from an appSession object and, when the authorization is completed, appSession stored the access_token for future accesses.
If there is a valid access_token, every API call is signed to authenticate the source.
JoomGap appSession is a session object, a JG Library Session manager. It handles the access and persistence of these variables:
In Joocial, there are two pages to receive the API call and manage the user login. These are the pages:
Following the previous workflow description, these are the authorization function calls, via JG Framework / OAuth authorization factory:
JgOAuth - login() - Final Step
What is the role of the "plg_system_joocialgap" plugin? In Joocial design, this plugin implements JoomGap library (JgOAuthServer and JgOAuthSessionTokenStore) as separated download. In other extensions, JoomGap library can be packaged in your extension itself, inside the internal structure (without the additional plugin).
We welcome feedback! Leave a comment by clicking the icon in upper right corner of the banner.
Copyright © 2007-2016 Extly Extensions - All Rights Reserved.
Joomla! name is used under a limited license from Open Source Matters in the United States and other countries. Extly.com is not affiliated with or endorsed by Open Source Matters or the Joomla! project.