Within MagentoTM, you need to create an API-user for usage with MageBridgeTM. This API-user is connected to an API-role, and this API-role implies a set of permissions (Role Resources) to certain parts of Magento. To make it easy to configure, we recommend to select just all permissions for the API-user. But if you want to increase security, you need to know which resources are needed to run MageBridge. Here's a listing.
What kind of API resources are needed?
Note that this configuration is experimental and needs thorough testing before putting it into production
Within the Magento Admin Panel you can navigate to System > Web Services > Roles and select the current API user used within your MageBridge configuration. Under Role Resources you can select all resources (All) or select on those which are needed (Custom).
The resources are shown in a tree-like structure. As main categories you will find things like Catalog, Sales, Customers but also MageBridge. The actual number of resource categories depends on the Magento modules installed in your instance.
MageBridge API Resources
While MageBridge uses its own API to utilize the main tasks like user synchronization, Single Sign On, remote browsing and event forwarding, still in some circumstances the original Magento API is used. For instance, MageBridge API Widgets will use most of the time the regular Magento API (through XML-RPC).
As a minimum the API User needs to have access to the resources under MageBridge. If you just click on the box MageBridge, all child-elements will be selected right away.
Other API Resources
This is more complex. The PHP-code in Joomla!TM is able to utilize both the special MageBridge API as well as the regular Magento API.
At the time of writing the only extra resource needed by MageBridge is "Customer > Retreive Customers Info" (customer_customer.list plus customer_group.list), while all other resources are wrapped through the resource-group MageBridge. By looking searching the Joomla! code for the string "getAPI" you will find most if not all API-calls.
We expect more resources to be added in the future. These resources will most likely include the resource-group Customers (used by the upcoming MageBridge User Manager), but certainly not the resource-group Sales.
Tutorials on MageBridge administration
- Performance tuning with MageBridge
- MageBridge SEO Guide
- MageBridge scenarios
- Authentication guide for MageBridge
- Using MageBridge modules
- Step-by-step: Activating MageBridge plugins
- Upgrading Magento, Joomla! and MageBridge
- Configuring payment methods in MageBridge
- MageBridge Security Guide
- Step-by-step: Creating a MageBridge Menu-Item
- Step-by-step: Create a Magento API user
- How to use URL-suffices with MageBridge?
- Using MageBridge stores to load a different Magento theme
- Step-by-step: Adding a custom Magento block
- Managing MageBridge extensions
- Using the MageBridge Content Plugin
- Enabling SSL for MageBridge
- Prevent direct access to Magento
- Switching stores with MageBridge
- Migrating users between Joomla! and Magento
- Using MageBridge Product Connectors
- Best practices with MageBridge
- Using the MageBridgeLinks/JCE-plugin
- Moving a MageBridge site
- Importing and exporting users
- Two VirtualHosts but one domain
- Removing MageBridge
- Disabling user synchronization in MageBridge
- Questions to ask your hosting provider
- MageBridge caching
- Setting the MageBridge URLs in Magento
Tutorials on MageBridge integrations
- Language configuration in MageBridge
- Integrating MageBridge with other Joomla! extensions
- Step-by-step: Configuring sh404SEF
- Integrating JomSocial and MageBridge
- JomSocial profile-synchronization
- Overriding the JomSocial-connector configuration
- Working with JomSocial events
- Related products with the Joomla! Tags component
- Using Layered Navigation Pro with MageBridge
- Using HM_FeaturedProducts with MageBridge
