Onedrive for Business API strategy confusion (Office 365, sharepoint, Skydrive Pro) - sharepoint-2013

I am writing some Windows desktop software in C# that can access Microsoft Onedrive for Business. This software is for anyone to use to access their own OneDrive for Business account.
Looking at the latest online documentation it seems that Azure Active Directory is needed to access the API but i have had some success without using Azure using a method similar to this (although I do have some issues):
http://jomit.blogspot.co.uk/2013/03/authentication-and-authorization-with.html
My question is do I have to use Azure AD or is the above method still expected to work?
If I have to use Azure then who needs the Azure account, is it me or is it each user who will use my software?
I have downloaded other third party software that accesses my Onedrive for Business account and I did not have to do anything with Azure. I want my software to be as simple as possible for users to connect to their Onedrive for Business account.

If it is hosted in SP, then you do not need to do anything.
If it is hosted externally such as o365 apps, you need to register this app in Azure AD. This applies for office 365 apps or even apps that are hosted somewhere. Azure AD is important to authorize apps to use office 365, office 365 apps can be hosted anywhere.

Related

Creating a Mult-Tenant OAuth Client App

Essentially, I'm wanting to create an Oauth Client as an App so I can get data from Dynamics for multiple customers. Does anyone know if this is possible to do in AppSource or do you know of another way?
I have a service that will be served in a cloud different than Azure so there really isn't anything for me to submit as an App and I really don't want every customer to have to setup their own App that gives my service the privileges/access it needs, but it's looking like I may have to.
It sounds like you'll want to register an app with Azure AD (the OAuth2.0 service/identity provider for work and school accounts), and create a multi-tenant app. Then you can configure this app in the Azure Portal to get permissions to the APIs the app wants tokens to call (in your case Dynamics or the Microsoft Graph).
Once this app is written, you can code up your app using one of the Azure AD Auth Libraries. Here's some sample code for a .NET web API. You can find more code samples on Github and search active directory. Moreover, the Azure Active Directory Developer Landing Page is a great place to look for more resources on doing all of this.

How to setup an external developer for Access 365 Web App

Owner has a Sharepoint site and wants to host an Access 365 Web App on it.
How should the owner setup a new Access 365 Web App so he could hire one or more external developers later, so they would be able to access that Web App and do some additions? All kinds of additions - creating new Access objects, writing VBA code, accessing data records.
He just need to create users for these developers so they will be able to use o365 services including debugging, deploying apps on the tenant.

Admin SDK for multiple google apps accounts

My team is trying to develop a product for the google apps marketplace and I am having issues with the workflow in the new ADMIN SDK.
With the now deprecated Provisioning API we simply ask for a username and password from the account we are trying to manage.
With the ADMIN SDK it seems as though they would need to go enable the API, create a key and do a lot of manual work for this to happen. This really is a tough option for us as the technical level of our clients is not likely to be able to make this transition.
Is there something like the work flow for the provisioning API where they can enable management from a third party or a recommended workflow for a developer to build an application that can access any number of google apps accounts?
A use case for this is say I want to develop a different option for a console, I want to build a console web app and simply ask for credentials or easy setup routine and allow our users to manage their google apps account in a different way.
Thanks in advance,
Steve
The Admin SDK Directory and Reports APIs work correctly with 2-legged OAuth 1.0a which is what the Google Apps Marketplace currently supports and automates. You do need to turn the Admin SDK on under "Register for additional APIs" from your Vendor Profile page on the marketplace. Also, the Administrative APIs for the domain must be turned on. You'll get a generic error that the domain cannot use the APIs if it's off in which case you can direct the client to the exact CPanel page where they can turn it on.

Where do I start making a web service for wp7 to windows azure db

I'm writing an app which I need to store user details, location and connections in azure db but have no experience with cloud storage. I have created my azure database but not sure how to communicate with the wp7 app. Any thoughts on where to start with the web service,
Thanks, MH
The following may point you in the right direction "Using Windows Phone with Windows Azure
" :-
http://msdn.microsoft.com/en-us/library/windowsazure/hh689721(v=vs.103).aspx
http://windowsteamblog.com/windows_phone/b/wpdev/archive/2011/08/31/building-windows-phone-applications-using-windows-azure.aspx
As to windows phone azure project, do you mean Windows Azure Toolkit for Windows Phone? This toolkit is optional. It may help us in some cases, especially if we want to integrate with ACS. But a web service will be enough if all we need is to bring data to the phone.
Best Regards,
Ming Xu.
To add to Paul’s suggestions, the recommended architecture is: Hosting a service in Windows Azure (such as WCF Data Services). The service will talk to SQL Azure (if you use SQL Azure as the database). Client devices, such as Windows Phone, iPhone, Andriod, a web browser, and so on, will communicate with the service. If you use WCF Data Services, you can expose the data to clients via the OData protocol, which is supported by multiple devices. To get started with WCF Data Services, I would like to suggest you to check http://msdn.microsoft.com/en-us/library/cc668796.aspx. To learn how to consume OData in Windows Phone, please refer to http://blogs.msdn.com/b/phaniraj/archive/2010/03/19/developing-a-windows-phone-7-application-that-consumes-odata.aspx.
Best Regards,
Ming Xu.

How do I develop Salesforce API code for a custom object without Enterprise/Unlimited edition?

Background:
I'm building a small application that will be run daily, pulling data from our own in-house databases and sending it over to our corporate Salesforce instance. I've built a custom object (called Marqui_Instance) in our Salesforce instance to house the data. The app will be creating a couple hundred of these, and attaching them to various Account records.
The Problem:
Our Salesforce instance is Professional edition, which means I can't generate the WSDL for our instance, which makes me think I'm not going to be able to develop code that can create/edit/delete Marqui_Instance objects.
Before I start floundering around in the dark, I thought I'd post on here for advice. The only thing I can think of is to create an identical object in a Salesforce developer account, and use the WSDL from there... but then when I go to deploy the code in production, will it work? I'm scared that the WSDL from my dev account will have some guids or something similar, and my code will only work against the dev account.
If you get your application certified by Salesforce they will provide you with a "Partner Application API" token. Using this when establishing the Salesforce API session will allow your application to work with a professional edition org.
Alternatively, you can also obtain API access to a Professional Edition org by paying an additional fee. You will need to contact your salesforce.com sales person.
Update: Apparently the functionality is enabled by Salesforce internally using the informally named "Black Tab".
See also: Re: Use of the API and Salesforce.com Professional Version
Access to the web services API for Salesforce is only available in Developer, Enterprise, and Unlimited Editions.
I believe that you aren't allowed to login to the API, so even if you managed to generate a WSDL it wouldn't work.
See the full edition comparison chart [PDF].