I inadvertently created an app using an old Asana account that I'd now like to deactivate. I'd like to transfer ownership of the app (keeping the same client ID) to my actual active account. Is there a way to do this?
I could create a new app (with a new client ID) on my active account, but I'd then need to ask all my users to re-auth, which I'd like to avoid.
I work on the Asana platform team.
Unfortunately, there is currently no way to transfer an app's ownership from one Asana account to another.
Related
Can I get the team_id for a user using app store connect api? I have looked https://developer.apple.com/documentation/appstoreconnectapi/users but don't see anything. I don't necessarily need it for a specific user but the team id related to that particular app.
The App Store Connect ID works via issuer-id and no longer exposes old / legacy identification like team_id or portal_team_id similar to how fastlane uses it via web authentication: https://github.com/fastlane/fastlane/blob/48151291f2c4949c3b1b9919ba2cc81a7cc33293/spaceship/lib/spaceship/portal/spaceship.rb#L42
An ASC API key is only ever valid for one team, therefore in the API logic it should also not have access to that information.
I want to develop and publish a bot for Teams, to interface with my SaaS (I already have a Slackbot that I'm porting). I'm creating a Bot Channel Registration as per this guide and came across the choice of whether to auto-generate a new App Id and password, or manually registering one (described here). I already have an Azure AD app for my SaaS that is published to the AppSource marketplace (the integration currently mainly allows logging in with your M365 account and syncing users from AD). Is it possible, and would it make sense to use the same App ID for the bot I'm developing for the same SaaS? Or is it somehow not advisable? And relatedly, can I expand my existing listing on AppSource to also contain the new bot, or should this be a separate listing?
I noticed in the documentation for manual registration of a bot, that it says that bots only work with "Accounts in any organizational directory and personal Microsoft accounts (e.g. Xbox, Outlook.com)" - my existing app only works with organization accounts, not personal accounts (since it's a B2B app) - does that change things?
Perhaps consider the question the other way - is there any good reason TO re-use the app ? It's very easy and basically free to create an additional app, and that way you don't run the risk of possibly ending up with settings needed for one scenario that conflict with another scenario's requirements, now or in the future. Here are some other possible considerations though:
new apps require Publisher verification, since 9 Nov 2020. This won't affect you for an internal app, which can be consented to by a global admin.
If you need the user (or admin) consent for some set of privileges (e.g. delegated Graph access), then using the same app might make sense. An example, in a Teams context, might be a bot and a tab that both need to access something from the Graph on the user's behalf. You could get consent in one context, and use it to access the resources from both contexts.
In a nutshell, and especially without a really really good idea of both of your current and planned use cases, it's hard to give a really solid 'yes' or 'no'. My gut says go with a separate app for a separate, unrelated scenario though.
Reusing the same appid against any other B2B won't create any problem. Being said that you can't use the above app if you're planning to implement/use BOT framework with it, as it's registered for organization only.
If you plan to create BOT related app registration then i would
suggest you to create new app registration with Organization +
personal for you scenario.
Please see the documentation and it's disclaimer:
In the above document it's pretty clear if you create any other app registration (other than Organization + personal), then the BOT will be unusable.
I want Teams users to use my Bot.
But I don't want to inform the MicrosoftAppId of the Bot for the users.
According to this site : https://msdn.microsoft.com/ja-jp/microsoft-teams/botsadd
I tried the way 1(select Add to Microsoft Teams) and the way 3(Get or create a deeplink)
(I skipped the way 2 since it needs information about MicrosoftAppId)
Those ways worked for users using Teams in Windows PC.
But they never worked for users using Teams in iOS Moblie.
So, how can I solve the problem?
Is there any other way to let the users use my Bot without inform the MicrosoftAppId?
The implicit registration of a bot from mobile device is not supported yet. In order to discover a bot, user need to invoke the bot at least once from desktop client/web.
Alternatively, you could sideload your bot in perticular team by creating an app manifest file. Sideloaded bots can be discovered by all the members by bot name.
Currently I have configured Quickbooks online API functionality for single user. which gets customers/bill information from quickbooks online using OAuth. It is working perfect.
I want to do the same functionality for multiple users.
Now there are many user's of quickbooks who have their own quickbooks online accounts and all these users are present in my custom application.
Is it possible to setup API functionality using keithe palmar's dev kit for different users to have API access? which things needs to be configured to make it run?
Is it possible to setup API functionality using keithe palmar's dev kit for different users to have API access?
Yes.
which things needs to be configured to make it run?
There is a variable $the_tenant that needs to be unique to each separate QuickBooks Online company you want to connect.
If you're building a multi-tenant type SaaS app, then you probably have a unique identifier for each of YOUR tenants already. So, set $the_tenant to your unique tenant ID value.
Done. That's all you have to do.
Relevant code:
// The tenant that user is accessing within your own app
$the_tenant = 12345;
https://github.com/consolibyte/quickbooks-php/blob/master/docs/partner_platform/example_app_ipp_v3/config.php#L57
All of the OAuth stuff is stored/based on that $the_tenant variable, so just make sure it's set to your unique tenant ID, and you're good to go. Note that you'll have to connect each individual QuickBooks company separately.
All that I have researched integrating Dropbox iOS SDK requires logging in to authenticate/authenticate a user.
But this is what I want to accomplish
Use only one user account. (Without authorization)
Create a random public folder(in same account) and upload files to that folder.
Get the folder link.
It's basically sending generated files from the app to an account.
How can I possibly do this?
The API was designed with the intention that each user would link their own Dropbox account, in order to interact with their own files. However, it is technically possible to connect to just one account. The SDKs don't offer explicit support for it and we don't recommend doing so, for various technical and security reasons.
For example, any user who extracts the access token from your app will be able to read every file in the Dropbox account, delete everything, replace it, etc.
However if you did want to go this route, instead of kicking off the authorization flow, you would manually use an existing access token for your app. (Just be careful not to revoke it, e.g. via https://www.dropbox.com/account/applications.)