I'm using the Microsoft Graph API to get webhooks for an email account.
While this seems to work fine for enterprise accounts (Office365) using the v1 endpoint, it seems I need to use the beta endpoint for personnal accounts (Hotmail, Live.com, Outlook.com etc.).
I'm not especially confident using something label as beta should I be worried? Is it reliable or is it going to break someday?
Thanks!
The /beta version of Microsoft Graph is a true "beta" and generally should not be used in a production environment. They can, and do, have breaking changes roll in without warning. They are intended for testing and future development, not for day-to-day use.
From the documentation:
Expect breaking changes to the beta version from time to time. Do not take a production dependency on /beta APIs.
also
We make no guarantees that a beta feature will be promoted to the current version. When the Microsoft Graph API team believes that a beta feature is ready for general availability (GA), we will add that feature to the latest current version.
Related
I have application on App store. I want to add support for Citrix MDM solution, which will allow end user to install application as in-office app.
Want to know what are the steps I need to perform in application?
I have gone through the details on citrix and got following information in bits and pieces and have some question on top of information
Need to use the MAM SDK in iOS app. From where I should Download the SDK? Is it freely available for POC purpose?
If I integrate the SDK what are the changes I need to do in application? any sample application available?
Need to wrap the iOS application . Is it required if I use MAM SDK?
My application communicate with my server and has user authentication. Do I need to change anything on my server?
Is dummy/temporary server setup of Citrix is available to test my application?
Let me tackle each question.
You'll want to download the MAM SDK from the citrix.com web site. To do so though you'll need to first create a user account. It is free to download.
The changes to your iOS app are fairly straightforward. I won't repeat them here, but in the MAM SDK download you'll find step-by-step instructions on what you need to do. There is a sample app with source code provided.
You no longer need to MDX Wrap your iOS application. That's the older way of getting your apps managed by Citrix Endpoint Management. The new MAM SDK approach replaces that mechanism.
There are no changes needed to your authentication.
There's no dummy server available, but you can request a trial site. Create an account at Citrix Cloud and request a trial of Endpoint Management.
Source: I'm an engineer for the Citrix Endpoint Management product.
Microsoft Intune MAM policy block data transfer to untrusted apps, based on https://learn.microsoft.com/en-us/intune/apps/app-protection-policy-settings-ios#data-transfer-exemptions, I can add a exemption for DocuSign app, but I need the iOS URL Protocol/Scheme of DocuSign, does DocuSign has that? If so, what's it?
https://www.docusign.net/restapi/help lists the endpoints. Does that help?
Version v2 and v2.1 are current. v2.1 is recommended for all new applications.
(There are no plans to remove v2 end points. Existing apps that use v2 do not need to update to v2.1 unless they want access to new features or fixes that are not security-related.)
I am integrating Onenote with my application. I am using MS Graph API's for getting data from Onenote. To consume the api's I am generating the token as mentioned at link get auth tokens.
I am registering my application at MS application registration portal. Do we need to purchase any kind of paid license to use services provided by MS graph API's.
The app registration process seems simple and doesn't differentiate between applications that can be used in production/test environment.
The app registration process seems simple and doesn't differentiate
between applications that can be used in production/test environment.
Apps registered in the app registration portal can be used for production or test environments. There isn't any switch that needs to be set when you're ready to ship. Congrats on shipping your app to production!
Do we need to purchase any kind of paid license to use services
provided by MS graph API's.
We don't charge for access to the API. Some of the services exposed in Graph via APIs require licenses like Intune. It sounds like you're using OneNote so as long as users of your app are already using OneNote you're fine to access their notes via our API. Just be sure not to DDOS us :)
If you can share, our community would love to hear about your app!
I'm using Google Cloud Platform. I have a Google App Engine project with its code stored in a git repo in my Google Developer Repository. I then use YouTrack to track bugs and would like to integrate it with my Google Developer Repository VCS. I'm able to use git repos with YouTrack, but it requires an Oauth2 Token.
It seems Oauth2 tokens are available for most Google APIs, but I don't know what API should be used by a 3rd party tool wishing to watch for commits. I assume this is the same problem faced by those wanting to use Jenkins to monitor their Developer Repo and perform testing and deployments accordingly.
How is this normally done? (ie get Oauth2 token and allow repo access to a 3rd party tool)
YouTrack only supports integration with GitHub/GitLab/Bitbucket directly, so solving the login issue does not unfortunately make any sense.
A workaround would be to use TeamCity or Upsource as sort of a bridge between YouTrack and your VCS. For more details see https://stackoverflow.com/a/9190486/469159. The answer only mentioned TeamCity, since Upsource had not been released at that moment.
I am building a twitter application that is currently using the classic login instead of OAuth. Does Twitter have any plans of deprecating this? I chose not to do OAuth because it is still being piloted as a beta.
I doubt there are any plans to deprecate the old API, because there are hundreds of applications which are designed to use it. Even though it's safe to use the old API, if I were you, I'd transition to OAuth due to user security concerns. OAuth is more secure than the plain API, and provides fewer ways for an attacker to obtain the user's password.
From the Twitter API documentation:
OAuth is the Twitter preferred method
of authentication moving forward.
While we have no plans in the near
term to require OAuth, new
applications should consider it best
practice to develop for OAuth. We
eventually would like to suspend Basic
Auth support. However we realize that
Basic Auth has been a large part of
the API's success, and that the
barrier to entry if OAuth is the only
solution is substantially higher. Many
applications rely on Twitter accounts
as their means of account management.
Additionally, Basic Auth allows a
developer with a command line, cURL,
and his account credentials to start
poking at Twitter data. There are
still a number of archetectural use
cases to work through before we
consider the deprication of Basic
Auth. Before any changes begin to
happen, we will discuss them with the
community through the support
channels, and give at least 6 months
lead time before making any policy
changes.
"When are you going to turn off Basic Auth?
We announced in December of 2009 the deprecation of Basic Auth. Its removal date from the platform is set for June 2010. We announced towards the end of June 2010 that we have postponed this until August 16th 2010."
--from http://dev.twitter.com/pages/oauth_faq
I believe using Oauth would be the safest bet, and its more convienet in the long run. I read an article saying that twitter is making Oauth mandatory pretty soon as well so you will have to switch over eventually.
It would be best if you provide both mechanisms to your clients, by default the classic login but if user is concerned about security they can choose the OAuth mechanism.
Mind it, many users will leave your application just because it requires them to give your application their (user's) credentials.