we have developed an app and distributed it through our organization's internal portal using apple enterprise account. Now we want it to distribute it privately in the App store account. We have both AppStore and enterprise account of our organization. Do we need to change the bundle id of the app, if upload the same app for private distribution because it is registered with an enterprise account?
It always suggested to use unique Bundle ID for each app. Also consider using different bundle ID for the App which goes into Private Distribution.
Related
So I have this really old UWP app that has been using the Live/OneDrive SDK to provide authentication and identification for at least 7 years now. The app is registered with Microsoft Account Authentication which provides a Client Id and Client Secret to identify the app when an authentication request is made.
When I use the SDK for authentication (OnlineIdAuthenticationProvider), it returns a unique Id (CurrentAccountSession.UserId) with which I can determine which of my users is using the app and then use that unique Id to persist/retrieve information the user provides.
The problem is....The OneDrive SDK is super old (hasn't been touched in over 3 years), outdated (.NET 4.51...no .NetStandard implementation) and Microsoft is pushing everyone to use MSAL and Graph instead. Fine.
But how can I do that and still be able to tie the person who is logged in to the app to the information I am storing for her/him?
From what I'm seeing, in order to use the new SDKs, I have to register my app, again, in the Azure portal and use a new Application (client) ID. If so, when my user logs in...my expectation is that any identifier that's returned to my app in the authentication process will not be the same as the UserId I've been using for almost a decade.
Has anyone done this? I can't be the only person who has encountered this problem...can I?
Any help would be greatly appreciated....
I want to restrict the access of google app engine apps only to users in my organization. Also, I want them to be able to access these without connecting to the organization's VPN
I am using python 3.7 runtime and standard environment for apps deployed on app engine
Using login: required handler is deprecated in python 3 runtime
handlers:
login: required
Is there a similar and ready to use alternate to this?
You can take a look at Identity Aware Proxy. Visit this link for a quick tutorial.
A benefit with IAP is that you don't need to make any changes to your application for it to work. All requests to your application will get authenticated with a google account and reach your code only if the user is logged in with a valid google account with IAP-secured Web App User role assigned.
You can create a Google Group in your organization's G Suite which contains all the users in the organization and assign the IAP-secured Web App User role to it. Then only users in your organization will be able to access the application.
Few questions I have as below:
Is the procedure for registering, submitting and installing the Public app is same for Private app also?
Private app uses Basic Authentication and can only be used by a merchant for his store specific requirements or customizations only. It cannot be used by other merchant, right?
How a merchant can create and install Private app on his merchant control panel? How it will get listed on the merchant's store control panel?
In the documentation, a private app technically refers to an app that uses basic authentication. It doesn't require registering, submitting, and installing, just the transference of auth credentials. If you wanted to have a "private" app that uses OAuth credentials (anything using OAuth is referred to as a public app in the docs), then you'd need to keep your app in draft status and the process would be the same as you described.
A private app could be used by multiple merchants, but it wouldn't be discoverable in the app marketplace. This was our old method for integrating apps and we recommend using OAuth.
Basic auth apps cannot be visible in the control panel. Only apps that use OAuth can.
I'm trying to find out how Google Cloud Messaging should be setup for businesses.
Currently I'm using my private Google account to manage the Google Developer Console and create a GCM project for my application. But what if I where e.g. a consultant agency developing an app for a customer, how would GCM be setup then?
I'm trying to answer the following questions:
Is there a way to create a Google account for Business that should be used instead?
Is it still free of charge?
Should the customer have and manage this account or do I as a developer/provider of the app manage this account?
Thanks in advance
From the documentation:
Google Cloud Messaging (GCM) is a free service that enables developers to send messages between servers and client apps.
Your Questions:
Is there a way to create a Google account for Business that should be
used instead?
Gcm does not require a special type of Google Account. Once you can create a Project in the Google Developer Console then you can use GCM with that project.
Is it still free of charge?
Yes it is free, even in business use cases.
Should the customer have and manage this account or do I as a developer/provider of the app manage this account?
This is up to you, it would depend on what the future relationship between the developer and the owner of the application is.
I'm just getting started porting my old code over to the new google apps json service but I'm not clear on the oauth.
I'm looking at:
https://developers.google.com/admin-sdk/directory/v1/guides/prerequisites
It says:
"Set up a new project in the Google APIs Console and activate Admin SDK service for this project. See the Google APIs Console Help in the upper right corner of the Console page for more information about creating your API project. "
My product gets installed at each client location. Do I create the app using my key then distribute this to my customers or do I use their key in my app that runs at their site? Do I also need to enable the admin SDK in addition to enabling API access?
Do I create the app using my key then distribute this to my customers or do I use their key in my app that runs at their site?
Do they have access to the source code? If true then it will be known to them.
Whether it is your key (an API project owner by you) or theirs depends on the kind of software you offer (tailored or common service (webapp?)) and who will be responsible of the quotas, billing (if needed) and maintenance.
Do I also need to enable the admin SDK in addition to enabling API access?
Yes.
FYI:
API projects can hold up to 20 accounts
Users can own several projects (don't know how many)
Projects can be shared with other users or Groups