We are trying to make a google cloud platform app Internal, but despite being logged in as a google workspace user, the 'Make Internal' button is greyed out with the message 'Because you're not a Google Workspace user, you can only make your app available to external users'.
We are logged in to the console as a Google Workspace user created specifically for this purpose. How do we enable the 'Make Internal' button so we can publish our app internally?
Related
am not able to retrieve the App basic information for slack-app developed by another member in my workspace
after accessing api.slack.com/apps only my own apps are displayed, how I can retrieve other apps developed by another member in my workspace.
I was expecting to display all apps owned by my workspace
only my own apps are shown
Due to the security architecture of Slack you can not see the app details like its client ID unless you are the owner of the app or the app owner has granted you permission. Your role on the workspace (e.g. admin) does not matter in that regard.
App owner can add additional collaborators for their app. Those collaborators will have the ability to see all details of an app incl. the client ID.
See also this topic:
Best practice to manage app ownership in Slack
I am building a Slack App and planning to distribute it in the Slack App Directory so that other users can install it. I am using Slash commands for this app. Now when I get my API called after some user type my Slash command then I want to access some of the user information using WEB APIs. But to access the info I need user token to call the WEB API. With Slash command request object I am not getting any user token. So my question is how can I get the user token at this time to access the information. Do I need to save this when user installs the app or do I need to provide the Add to Slack button for this?
Yes, your app will receive the access token for a team / workspace only as result of a successful installation process and should then store it together with the team ID for later use. Each slash request includes the team ID which allows you identify the correct access token for each team.
There are two approaches for installing Slack apps, which can be chosen on the "Manage your apps" pages under "Basic Information". Here is how it looks:
Installation from landing page
Having your own website with a "Add to Slack" button is the easiest way to to that. You website will then need to handle the installation process, which basically is a Oauth flow. You should also make sure to request the right permissions, so that you can later access the API methods that you need. This installation approach is called "Installation from landing page".
Installation from App Directory
Another way to install your app is "Install from App Directory". This will allow users to start the OAuth process directly from the App directory, instead of having to click a "Add to Slack button" on a website. Its has the same effect as clicking a custom "Add to Slack button", so you still need a website behind it to handle the full OAuth flow.
Important: This option is only available to apps that have been approved by Slack and are listed on the App directory.
Further Reading
Installation approaches
Oauth process with Slack
I am trying to configure the Google Apps Marketplace SDK and get the following error when clicking on the Configure Tab.
"The API "appsmarket-component.googleapis.com" doesn't exist or you don't have permission to access it"
However when I check for enabled services in the project it shows as enabled.
**$ gcloud service-management list --enabled
NAME TITLE
appsmarket-component.googleapis.com Google Apps Marketplace SDK**
Any pointers on how to resolve?
Note: I did setup the G-Suite account for the site just a couple of days back and so am still in the Trial period. Not sure if that has any impact on access to the API's?
We have review apps enabled for our app in Heroku. The feature was enabled by a developer who no longer works with us. When we revoke his access to the app from which the review apps are build, the review apps are not built any more. If we disable and re-enable the review apps, Heroku assumes we are doing so as the original user so we get an error message that we don't have access to that app...
Is there a way to switch the owner of the automaticlly built review apps?
Here is the response I got from the Heroku support:
You can fix this by visiting your pipeline, clicking "Manage GitHub connection", then clicking "Disconnect". Wait a few seconds, refresh the page, and reconnect from the same menu. This will make you the default user for provisioning and deploying review apps.
Once that's done, you'll need to re-enable review apps for your pipeline. Also, if you had any apps set to auto-deploy from GitHub, you'll need to configure that again as well.
Following these instructions: https://developers.google.com/google-apps/extensions-console/
I am unable to deploy an in-house Contextual Gadget to a Google Apps Domain.
Creating, assigning Manifest/Extractor(including validation) and deploying appear to work fine, however Granting Access results in a 302 (redirect) to the Google Apps Admin Console and the Gadget does not show up in the Marketplace Apps Management console.
UPDATE - Developed a workaround
1) Follow instructions https://developers.google.com/google-apps/extensions-console/
2) Then go to https://console.developers.google.com/project and select your project
3) APIS & OAUTH -> Credentials -> Create new ClientID
4) Select “Service account” then “Create Client ID”
5) The private key is not necessary for this process and can be discarded. Press “Okay, got it” button.
6) Go back to the Marketplace Apps console: https://admin.google.com/AdminHome#AppsList:serviceType=MARKETPLACE and select your project
7) Select “Data access”, then “Grant Data Access”
The Contextual Gadget should now be deployed and have the correct permissions
The way described at https://developers.google.com/gmail/contextual_gadgets seems to be totally outdated. Even the form in the Google Apps console for gadgets seems to be outdated.
You need to follow this description: https://developers.google.com/apps-marketplace/preparing
Contextual Gadgets are now developed using the API console (not app console) and there is a form to create the extractors etc.