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.)
Related
Google assistant sdk announced that early this month they will deprecate OAuth using client key for their voice assistant development modules. I am using python to run a fez of the sample conversation codes like text-to-speech and push-to-talk.
Although the old oauth may continue to work with test accounts, on publish it would no longer support oauth.
I have 2 questions:
What is the limit of requests I can send over a test account- per day, per project. Can it be increased to a higher number of requests?
Since OAuth uses key generation using a googleauth package installed over pip, is there any alternate way of authentication to now continue using the service? Even if oauth has been deprecated the documentation for the assistant sdk setup remains the same- It shows the old way using the client secret key.
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.
I have an application for my client that uploads videos on youtube on behalf of my client.
What my client do is provide his user name and password in my app and then app uploads videos using Youtube DATA API V2(Username/password credentials).
But since username/password authentication mechanism is not available in V3, I have to change the user involvement that is required in the new Authorization mechanism. But my client is does not agree.
The question is, what if I continue to use API V2 and not switch to V3. Is there any chance that Google will stop V2 and I have to move to V3?
Is there any way I keep authenticating using credentials and not switch to OAuth 2.0?
You asked: Is there any chance that google will stop V2 and I have to move to V3?
Short answer: You need to switch to YouTube's v3 API.
From Google:
The YouTube Data API (v2) has been officially deprecated as of March 4, 2014. Please refer to our deprecation policy for more information. Please use the YouTube Data API (v3) for new integrations and migrate applications still using the v2 API to the v3 API as well.
If you haven’t yet migrated from the previous API version (v2), we wanted to remind you it will be unsupported as of April 20, 2015, and shut down soon thereafter. To make it fast and easy for you to migrate, check out the new Migration Guide. It’ll help you identify the v3 API methods and parameters that correspond to the functionality that you've been using in the v2 API. It also points out new features that the v3 API supports.
Source
Your second question: Is there any way I keep authenticating using credentials and not switch to OAuth 2.0? I do not know the answer to. Maybe ask as a separate question?
As per Dropbox REST APIs documentation, the login process has to go through OAUTH Urls like https://api.dropbox.com/1/oauth/request_token. But dropbox's iOS SDK makes a call to https://www.dropbox.com/1/connect_login which is not documented anywhere. I want to use REST APIs in my application, but I want to display same authentication screen as done by dropbox SDK.
Did anyone face this problem? Does anyone know what dropbox says about using undocumented APIs like connect_login?
The latest word from Dropbox on /connect_login is:
That's a special endpoint for the iOS SDK, because of the specific requirements for App Store approval. You should use the official SDKs as provided, and we'll provide updates for these over time.
(taken from https://forums.dropbox.com/topic.php?id=104267)
Currently Google is migrating their old Google Data API to the new Google API.
When we do API queries over the old Google Data API, we usually use Zend Framework and the given consumer key/secret to do the authen/autho, which is fine.
Question is, is it possible to use the given consumer key/secret (from the Google Apps Marketplace listing) and the new OAuth 2 Library to call the API? What I have been having is the error message redirect_uri mismatched issue and obviously Google Apps Marketplace provides no way to change this value. Even though they had provided a link for us to go to the API Console from the listing page, I cannot see the OAuth 2.0 options in my API Access page at all.
Did I missed out anything?
If let's say I need to use the Google Apps Admin Settings API, does it mean I need to separately create a new OAuth 2.0 API Access in the API Console, then, when I need to access user data, I need to do the Auth flow again using this new consumer key/secret/redirect? I can't set this permission in the Listing Manifest? (Not supported?)
Thanks for the clarifications!
Google Apps Admin Settings is not yet migrated to the new google-api, AFAICS. Check out this list : http://code.google.com/p/google-api-java-client/wiki/APIs ;
you can however use the new google-api client libraries but you have to roll your own XML model for the given API, it is not so hard, I did a similar thing for the Contact API;
The consumer/key secret can be re-used normally if it is sufficiently scoped. A related project for your market app is automatically created in the Google Api console from what I remember..