Tg Resolve Domain Uncensored Channel
⚡ ALL INFORMATION CLICK HERE 👈🏻👈🏻👈🏻
Tg Resolve Domain Uncensored Channel
Нажмите alt и / одновременно, чтобы открыть это меню
Перетащите, чтобы изменить положение
Открыть Страницу «Tg:resolve?domain=B29ClubBot» на Facebook
Открыть Страницу «Tg:resolve?domain=B29ClubBot» на Facebook
Facebook показывает информацию, которая поможет вам лучше понять цель Страницы. Просматривайте действия людей, которые управляют контентом и публикуют его.
Электронный адрес или номер телефона
How to create 🔗links to phone, WhatsApp, Telegram, Skype etc.
Tg : resolve ? domain =B29ClubBot - Home | Facebook
Telegram passport
tg - resolve - npm
problem with links like “ tg :// resolve ? domain =” and... | WordPress.org
Главная
FAQ
Приложения
API
Протокол
Схема
О Telegram
FAQ
Блог
Вакансии
Для мобильных
iPhone/iPad
Android
Windows Phone
Для компьютера
PC/Mac/Linux
macOS
Веб-версия
Платформы
API
Переводы
Instant View
Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn‘t have access to the users’ personal information thanks to end-to-end encryption.
This page describes the request flow that client apps must used to send the requested data to the service.
From the perspective of a service that requires real-world ID, the process looks like this:
See As a bot to see how to request passport data using a bot, through the MTProto API.
Look at the Passport Manual to see how to request passport data using a bot, through the simplified bot API.
From the perspective of a user, the process looks something like this:
See As a user to see how user client apps should send passport data to a service, through the MTProto API.
A simplified version of this process can be used using the bot API, for more info see the Passport Manual .
Using the MTProto API, the process is pretty much the same, up until the actual API calls.
Note that all binary fields are in raw binary format, unlike in the bot API where they are base64-encoded
When the user confirms your request by pressing the 'Authorize' button, the MTProto API sends an updateNewMessage from the user, with a messageService constructor, containing a messageActionSecureValuesSentMe constructor that contains the encrypted Telegram Passport data.
To decrypt the received data, first, decrypt the credentials contained in secureCredentialsEncrypted .
Decrypt the credentials secret ( secret field in secureCredentialsEncrypted ) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)
Use this secret and the credentials hash ( hash field in secureCredentialsEncrypted ) to calculate credentials_key and credentials_iv as described below:
Decrypt the credentials data ( data field in secureCredentialsEncrypted ) by AES256-CBC using these credentials_key and credentials_iv . IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )
Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.
Note that all hashes are raw binary data, not hexits
The credentials are a JSON-serialized object, structured exactly as in the bot API » .
Since decryption credentials are E2E encrypted, apps have to store the decryption credentials as JSON and not TL payloads.
The credentials are used as described in the Passport Manual to decrypt the files attached to the secureValue .
In this case, the container for the E2E encrypted data is in TL, while the encrypted data itself is in JSON.
The scheme for the secureValue constructor defines the constructor that can be found in each field.
Here's a list of possible SecureValueTypes , and the parameters that can be set/requested when using each type.
Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type .
DataCredentials extracted from the credentials can then be used to decrypt encrypted data from the data field in secureData .
For more info on how to decrypt the data field, see the passport manual .
Files (JPG format when decrypted, max. 10MB) are downloaded chunk by chunk as described in files » , except that instead of generating an inputFileLocation , an inputFileLocation should be generated, instead.
FileCredentials extracted from the credentials can then be used to decrypt downloaded encrypted data.
For more info on how to decrypt passport files, see the passport manual .
The email/phone is passed in plaintext using the respective SecurePlainData constructor.
Emails and phone numbers sent using telegram passport are already verified as described in the passport manual .
If the data you received contains errors, the bot can use the users.setSecureValueErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.
Descriptions of the method parameters can be found in the method's documentation page » .
The process starts when your app receives an event from one of the SDKs , or from a custom source.
The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:
With the following query string parameters:
Example URI, generated by the Telegram Passport Example page :
This object represents the data to be requested.
This object represents a requested element, should be one of:
Passport document type identifiers are aliased with the following reduced type identifiers:
You can use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".
This object represents several elements one of which must be provided.
This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.
You can also use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".
The next step for the client app is to request the user's 2FA passport, and configure Telegram Passport/fetch and decrypt remotely saved Telegram Passport parameters as described in the Encryption article » .
Then, the client app passes the bot ID, scope and public key from the passport authorization request to the Telegram servers using the account.getAuthorizationForm method.
The response will be an account.authorizationForm constructor, with info about the required document types, the URL of the service's privacy policy, as well as info about the bot to which the form should be sent.
If the form was already submitted at least once, the constructor will also contain a list of already submitted data, along with eventual errors.
The user should accept the privacy policy and proceed to fill in the required data, and the client should encrypt and upload it as described in the Encryption article » .
Once the user finishes uploading the required documents and clicks on the submit button, the client calls account.acceptAuthorization , submitting the documents to the bot associated to the service.
Finally, the client opens the callback URL (if present).
If any of the values of the submitted form are rejected by the service, the bot calls the appropriate method to set information about errors .
The user can find out about these errors directly from the service, or, if they decide to restart the process and resend the corrected data, directly from the authorization form ( errors field).
Encrypted Telegram Passport element data
Encrypted passport file with the front side of the document
Encrypted passport file with the reverse side of the document
Encrypted passport file with a selfie of the user holding the document
Array of encrypted passport files with translated versions of the provided documents
Array of encrypted passport files with photos the of the documents
data , front_side , selfie , translation
data , front_side , reverse_side , selfie , translation
data , front_side , reverse_side , selfie , translation
data , front_side , selfie , translation
List of requested elements, each type may be used only once in the entire array of UriPassportScopeElement objects
List of elements one of which must be provided; must contain either several of “pp”, “dl”, “ic”, “ip” or several of “ub”, “bs”, “ra”, “pr”, “tr”
Optional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
Optional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
Element type. One of "pd", "pp", "dl", "ic", "ip", "ad", "ub", "bs", "ra", "pr", "tr", "pn", "em"
Optional. Use this parameter if you want to request a selfie with the document as well. Available for "pp", "dl", "ic" and "ip"
Optional. Use this parameter if you want to request a translation of the document as well. Available for "pp", "dl", "ic", "ip", "ub", "bs", "ra", "pr" and "tr". Note: We suggest to only request translations after you have received a valid document that requires one.
Optional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "pd"
