 Username, Password, and Security Token. (URL is optional; configure this only if you want to override the default URL.)
Click Test Connection to make sure the credentials are valid.
Obtain your user Security Token from your Salesforce account.
Create a new Mule Project and add an
sfdc:global-elementat the start of your file. Global Elements set up reusable connection parameters.
You must provide four required credentials: username, password, securityToken. The url parameter is optional. You can either directly provide these values in the fields or add parameterized references to a configuration file.
When adding a Salesforce message processor to a Mule flow, reference this global element through the attribute
config-ref. The topic value is required and is a text string used to group records around a common theme. Mule permits any topic string that Salesforce allows.
Best Practices
You can either hardcode your credentials into the Salesforce global configuration properties, or reference a configuration file that contains these values. For simpler maintenance and better re-usability of your project, Mule recommends that you use a configuration file. Keeping these values in a separate file is especially useful if you need to deploy to different environments (for example, production, development, QA) where your access credentials differ. === Full Code Example
The example below represents an example minimum configuration for a Salesforce connection using basic authentication.
OAuth Authentication
The Salesforce connector also supports authentication via the[OAuth] standard. The key benefit of OAuth is security for the end users of your service. Rather than supplying credentials directly to your third-party service (the OAuth client), a user only hands out security tokens that have limited scopes and duration. By giving a third-party service only limited access to his account, the user can mitigate his exposure; the more places where a user’s actual credentials are being stored, the greater the chance of one of these being hacked and used maliciously.
OAuth allows an API provider to:
Grant consumers of the API limited access to secure data
Avoid disclosing an end user’s access credentials to an API consumer
Retain the authority to revoke the consumer’s access to an end user’s secure data at any time
To connect to Salesforce through OAuth, you must first register your application and obtain a consumer token and a consumer secret. Keep in mind that neither of these are the same as the access token used in basic authentication; these tokens refer to your application, not to your user.
Once you have obtained these tokens, you must:
Configure a global element that contains the OAuth connection credentials you obtained from Salesforce. Be sure to configure a callback URL.
Create an authentication flow that includes an Authorize Salesforce message processor.
Create a flow that receives the already authenticated users. Set the address of this flow to be the Callback URL that you set up in Salesforce when registering the service.
For a detailed explanation of how perform these steps with Salesforce, read Using a Connector to Access an OAuth API.
Enabling SAML SSO in a Salesforce Connector
Implementing SSO over SAML gives organizations a solution to user management that separates service providers from identity providers. Salesforce currently provides support to different SSO and SAML configurations such as different SAML flows and by acting as both service provider and identity provider.
For integration purposes, SSO is not as useful because SSO is browser oriented and not application oriented. This makes SSO not suitable for an application integration development.
On the other hand OAuth2 is everything SSO is not on the application integration side. OAuth2 requires a single user interaction to authorize an application, and then the whole integration relies on a token stored in your application, that is, OAuth2 is application oriented.
Mule solves SSO integration with Salesforce by providing both SAML and OAuth2. The Mule solution uses OAuth2 to get a token. On the authorization step, instead of logging into Salesforce, logs in to an identity provider.
Configuring Salesforce for SAML and SSO
See Salesforce’s Configuring SAML Settings for Single Sign-On. Set up Salesforce SSO and SAML configuration according to your needs and your identity provider’s configuration.
Enable the
My domain feature and redirect all logins on the domain to your identity provider URL.
The
My Domain feature lets you select a custom domain name for your application. A
My Domain URL can be: for a production organization or for a Developer Edition. Configuring
My Domain enables support for single sign-on, improves the user experience, and allows users to access deep links into their environment using SSO.
Configure
My Domain using Saleforce’s Setup > Company Profile > My Domain. As users may not be authenticated when they arrive at Salesforce, a unique domain is the mechanism by which a specific organization’s SAML configuration can be discovered. To take advantage of SAML for desktop and mobile apps, deploy My Domain, which greatly improves the user-experience for web browser based single sign-on.
Mule Flow
Assumptions:
Salesforce SAML configuration is complete
Salesforce Application is OAuth2 enabled (Consumer Key, Secret and Callback URL)
Note : This flow may vary depending on your Mule application deployment. An < https:connector > is needed in case of cloud deployment (CloudHub).
Flow Explanation
At runtime, users access their Salesforce custom domain, which Mule stores. The authorization message processor uses the domain and Salesforce redirects the user to their custom domain’s sign-in page, which is their identity provider’s web page.
After logging in, the user is redirected to the resource requested initially which is the Oauth authentication request. The user allows the application, and the token is issued and stored at Mule.
The most important part of this flow is the ability to use MEL expressions at the <sfdc:authorize> message processor. This gives the ability to dynamically configure at runtime (and optionally per user) the OAuth2 endpoints.
See Also
Salesforce Connector Reference
Read about connecting to OAuth APIs with Mule
-
Refer to the[Salesforce documentation] about authorizing your service via OAuthWell there is a long time between now and when FFXIII comes out so let's not get ahead of ourselves here. Since Square-Enix are whores for playing the field I don't see FFXIII going cross platform but you do have to remember that FFXII had a console with an instalation base of 120million and was a follow up to perhaps the most successful GBA game of all time, Tactics Advance. FFXIII has quite the disadvantage compared to its predicessor, let's just hope that Blue Dragon doesn't deflate the hype for FFXIII or Square's ability to make fresh games.Railbanking is an agreement between a railroad company and a group or agency which preserves the future rail use of an out-of-service rail line but allows for other development in the interim, typically as a multi-use trail (my favorite of the possibilities). This shot from Billings shows a much more literal form of railbanking.My top ten books for an introduction to Buddhism, out of the hundreds that have been written, would be: 

* *What the Buddha Taught* by Walpola Rahula (general Buddhism)
* *A Concise History of Buddhism* by Andrew Skilton (the history of Buddhism, mainly it's rise and fall in India) 
* *The Dhammapada* of which there are many translations. (Mainly in the Pali tradition, extant in the Chinese, and translated in the 20th Century into Tibetan) 
* The Bhikkhu Bodhi series of the translation of the Pali Canon. This is a vast collection of the Discourses of the Buddha, *Connected, Short, Middle*, and *Long*. Not for the faint of heart and only if you're ready for a very big reading challenge. (Theravadin Tradition mainly) 
* *A Very Short Introduction to Buddhism* and *Buddhist Ethics* by Damien Keown (general Buddhism) 
* *Food for the Heart: The Collected Teachings of Ajahn Chah* (a personal favorite of mine, but it also gives a good introduction and a short history of the Thai Forest Tradition) 
* *The Fundamental Wisdom of the Middle Way* by Nagarjuna, trans. Nishijima and Warner (the foundational text of Mahayana philosophy) 
* *Tibetan Zen* by Sam van Schaik (another personal favorite, of the lost Samten tradition, the Tibetan equivalent of Chinese Ch'an/Japanese Zen)
* *The Story of Tibet: Conversations with the Dalai Lama* by Thomas Laird (more about the history of Tibet than Buddhism itself, but filtered through the Dalai Lama, it is primarily the most modern and recent history of Tibet by a Tibetan, filtered through a western journalist) 
* *Buddhist Warfare* ed. Michael Jerryson and Mark Juergenmeyer (for a sobering take on how Buddhists of all traditions throughout history have failed to uphold the most basic precept)   


I'm sure those will keep you busy for a while. Let me know if you have any questions.I was lucky enough to be born into a horsie family, my father broke horses into harness and saddle and I was able to watch and learn these skills from a young age. I started my first horse under saddle at age 15 and have