Menu
Does anyone have any examples or advice for how to go about using oAuth to provide the authentication mechanism for an API that should be publicly exposed?
Specifically I'm talking about being an oAuth provider for my own API, not integrating or authenticating with anyone else's API.
For example, I wish to be able to issue API keys to developers that they can use to authenticate and access my API, much in the same way Flickr does, and as far as I believe oAuth can support this, but I'm not sure how the solution would be structured?
458
Tangible Real Accounts. Tangible Real Accounts are accounts which have physical existence. In other words, such assets can be seen, felt or touched. For example Machinery A/c, Vehicle A/c, Building A/c etc.
Though there are twelve branches of accounting in total, there are three main types of accounting, according to McAdam & Co. These types are tax accounting, financial accounting and management accounting.
Take a look at the three main rules of accounting: Debit the receiver and credit the giver. Debit what comes in and credit what goes out. Debit expenses and losses, credit income and gains.
All assets of a firm, which are tangible or intangible, fall under the category "Real accounts". Tangible real accounts are related to those things that can be touched and physically felt. Few examples of tangible real accounts are buildings, machinery, stock, land, etc.
It appears that DotNetOpenAuth has an example by the way of the OAuthSeviceProvider project in the Samples folder included in the distribution. It's written in WinForms and isn't cleanly written but definitely serves as a good starting point.
113
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
