How to get verified badge in TTE?
Question about verifying account in Telegram Test Environment, how can I do? many accounts have verified badges with text i can do it by myself, but, i can't find how to do it. i checked a lot of documentations on telegram official website, api, some other websites such as https:// docs.pyrogram. org/topics/test-servers
I've already tried many variants but no one helps, so..
please help, where can i find documentation for telegram test environment.
Related
I integrated telegram login widget for my website several months ago.
It worked like a charm.
But it stopped working today.
enter image description here
IMO, the reason is that my Chrome browser has been updated recently, and banned third-party cookies.
Even telegram community has no solution for this yet.
Anyone can help?
Thanks in advance
Telegram responded so quickly to the changes of modern browsers' updates.
They implemented overcoming third-party cookies for telegram login widget.
For more information, you can refer this.
Is it possible to disable third-party cookies while on my site on behalf of users?
Google Cloud Platform's Tech Support directed me here.
GCP is telling me the add-on is "successfully verified and add-on is available for users." The OAuth Consent Screen confirms this.
In Developer Dashboard, the add-on is published. The "Publish in Marketplace" checkbox was checked upon submission for publication.
I've read through troves of online Google documentation, but still have not found the solution.
The docs add-on is OrangeSlice: Teacher Rubric.
ideas? Thx
It's here https://gsuite.google.com/marketplace/app/orangeslice_teacher_rubric/852746965799. You can find the link in the G Suite Marketplace SDK.
The answer is, I think, Google is very busy.
There are three advertised approval steps but it took more to get the add-on listed. It was approved first via Developer Dashboard crew. After completing the GS Marketplace Configuration and then the GS Cloud for OAuth, it was approved twice more. To the get add-on published, I needed to inform Developer Dashboard that it was approved by GS Cloud, THEN IT COULD BE RELEASED.
So if you're having issues, be persistent. The Google team answers nicely but many questions go unanswered or are ambiguous. There are many directions spread over several different pages: Marketplace, Cloud, Apps Scripts, OAuth App Verif FAQ, etc. They mostly concur but there is plenty of vagueness and inconsistency which only added to my confusion. I have 2 add-ons, one is a stripped down version of the other. The stripped down version had more hoops to jump through for approval-verification and then release than the fully loaded version. Not sure why. Again, the Google team is nice but it feels like they are swamped and/or have an intra-system communication challenges.
Here's an example.. directions within an email from the Google team:
Please follow the steps below to ensure your OAuth scope(s) request is submitted for review:
Sign-in to the Google Cloud Console
Select the project-id: api-project-#############
Go to Credentials on the OAuth Consent Screen
.....Credentials and OAuth Consent screens are two separate screens under the same heading, API Apps & Services. Neither exists within the other but next to each other.
So what to do?
my dev and I would like to implement the google picker on our website. It will allow the web-visitor to upload their files from their Google drive to our website.
My dev is now trying to get the API for the google picker however they are asking for a "demo video that showcases the process to request an OAuth token" and we were wondering how we should do it when we don't have the API from google.
We are doing all of this on the staging site and we were wondering how are we suppose to do this demo video when the API is not provided and not installed.
please enlighten us, thank you!
See the question How can I make sure the verification process is as streamlined as possible? in the FAQ. It explains what the verification team is looking for with the video. Mostly it's just about showing how your product uses OAuth and the various APIs -- in your case how it asks for access to Drive, how the picker is used, etc. You're showing the integration from the user perspective.
When I try to publish my app on the Gsuite Marketplace via GCP, I find no way to change the setting 'Visibility'. Event if the app has never been published.
Between the two options (My Domain - Public), My domain is selected and can't be switched to Public, so nobody has access to my app.
Any help?
I've tried to contact the support and find help on forums but no answer at all.
First step, I'd recommend reviewing Choosing where to publish to ensure that you've published to the correct location. As noted under Publish your app (before you publish), your app is reviewed to determine if it meets the requirements for the relevant store. Additionally, your application may also have to undergo OAuth verification (I think this could be the problem) , and security assessment if it accesses user data, such as Gmail, Drive, Contacts, or Calendar
If your app is exempt from verification or if you've already undergone assessment and been approved, and your issue persists, I'd recommend contacting Marketplace Developer Support, via the below steps, who can assist you with your publishing issue.
Navigate to the new Developer Dashboard.
Click Contact Us.
The Developer Support contact us form is displayed.
I've tried to contact the support and find help on forums but no answer at all.
How did you contact Google Support? They have many teams and sometimes agents are not aware of the scope of support. Personally I would contact GCP Support first to verify your App in GCP, once they confirm everything is working from their end they need to route the case to GSuite with an Admin Console specialist to debug the problem
We have a simple hangouts bot that has been working fine for several months. Starting yesterday 1 or 2 users indicated that they were receiving an error message when talking to the bot indicating that: 'Your administrator prevented you from talking to bots in direct messages'. Over the past 24-hours more and more people reported that the issue started happening to them until it was everyone. When it happened to me earlier today I messaged the bot 2 times about 5-minutes apart, it worked the first time then the second time I got the administrator prevented message.
I tested the #meet and #drive bot's and they both still appear to work.
I have confirmed that none of the settings on the bot have changed, most importantly that the 'Bot works in direct messages' option is still checked.
I have talked to our IT administrator who says that no settings have changed in our GSuite setup.
Looking through the documentation I can't find any mention of an issue or setting that would cause the above error. Is anyone aware of what could be causing the above.
Google Support statement
(...) if your domain currently applies a whitelist to restrict the set of G Suite Marketplace apps that users can install, existing internal bots may stop working. In order to appear and continue to function for users, the developers of these bots need to publish the bots to the domain as you can see on link. (...)
Solution
As said Jordansan this issue is related to the domain administration and to security enhancements. You may still use up to 5 email addresses to do your tests. Once you want your bot public, you will need to list it on the G Suite Marketplace.
To do so follow this guide Listing your bot on G Suite Marketplace. An extract is provided below :
G Suite Marketplace publication steps
This section tells you the specific steps you need to perform to publish your bot on G Suite Marketplace. The general steps are:
Create an OAuth client ID, if your project doesn't already have one.
Add the G Suite Marketplace SDK to your project and populate its configuration tab.
Populate the SDK's publish tab and submit.
The detailed steps for each of these are described in the following paragraphs.
For security reasons most organizations have (and should have) whitelisting enabled, which will prevent non white-listed marketplace apps to be enabled within the organization.
To deploy your bot you'll need to contact your GCP responsible and ask him to whitelist your bot.
Temporary solutions
What you can do is make the bot accessible to everyone in your organization. Assuming that the bot can be published.
If the bot shouldn't be public, you may implement your own connector to filter incoming queries and allow only selected email addresses. However the bot will still appear to everyone on the search screen, and everyone will be able to message it.
It's possible that your domain makes use of a new feature which requires bots to be whitelisted. This was introduced in a recent update. Previously, the admin setting was binary in that you could allow either all bots or none. Now any second party bots must be whitelisted if the administrator settings for that domain requires whitelisting.
You can find more information here: https://support.google.com/a/answer/6089179
I opened a ticket here: https://issuetracker.google.com/issues/137266964
Edit: We got this working by following the steps listed here: https://developers.google.com/hangouts/chat/how-tos/gsm-list and our GSuite admin white-listed the Bot for internal use. This eliminates the 5 user limitation and keep the current security settings in place for all other bots & GSuite Applications