Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A Biblioteca Common para revendedores do Android é uma biblioteca Java que interage com o
as APIs do Knox e a API de revendedores de registro sem toque para
fornecem uma única integração para o Programa de implantação Knox da Samsung
(KDP) e os serviços de registro sem toque do Google.
O KDP permite o uso
que os revendedores verifiquem dispositivos Samsung para clientes corporativos usando
Registro do Knox Mobile
(KME). Da mesma forma, o registro sem toque permite que clientes corporativos verifiquem e
configurar outros dispositivos Android
e compradas de revendedores autorizados.
Registre dispositivos Samsung e outros dispositivos Android com uma única integração.
A biblioteca do revendedor contém duas classes de fábrica: uma
para cada serviço de registro. Essas classes de fábrica aceitam contas de serviço
geradas pelo portal da API Knox Cloud da Samsung e pelo Console de APIs do Google para
autorizar chamadas para APIs do Knox e de registro sem toque para revendedores. Para mais detalhes, acesse Começar.
Use essas classes de fábrica para criar objetos ResellerService.
Um conjunto comum de métodos é
disponível para objetos ResellerService que permitem aos revendedores realizar tarefas
como atribuir e cancelar a atribuição de dispositivos de e para clientes.
Depois que um revendedor usar a biblioteca para atribuir dispositivos a um cliente corporativo,
o cliente pode usar o portal KME para criar e aplicar configurações para a Samsung
dispositivos e o portal de registro sem toque para criar e aplicar configurações a
em outros dispositivos Android.
Para quem esses anúncios são indicados
A Biblioteca Comum do Revendedor Android é destinada a revendedores de dispositivos que não
integradas ao registro sem toque ou ao KDP (em inglês).
Os revendedores que já fazem a integração com o registro sem toque precisam fazer essa integração
KDP separadamente
gerenciar dispositivos Samsung.
Os revendedores já fazem a integração com o KDP
devem usar a API reseller do registro sem toque para
gerenciar dispositivos que não sejam Samsung.
Exemplo de fluxo de trabalho
Veja abaixo um exemplo de fluxo de trabalho de como um revendedor pode usar a biblioteca de cliente
para gerenciar o KDP e
registros sem toque de dispositivos. Exemplos de código para executar tarefas básicas são
disponível em Vamos começar
e Operações comuns.
Receber ordem de compra
Um cliente corporativo envia uma ordem de compra. A ordem de compra
contém dispositivos Samsung e outros dispositivos Android.
Agora os clientes podem criar configurações e aplicá-las aos dispositivos.
Dispositivos Samsung: os clientes usam o
Registro do Knox Mobile
(KME) para criar configurações e aplicá-las aos dispositivos Samsung
foram atribuídos na Etapa 4.
Outros dispositivos Android: os clientes usam o
Portal de registro sem toque
para criar configurações e aplicá-las aos dispositivos que não eram da Samsung
atribuídos na Etapa 4. Se o EMM do cliente oferecer suporte ao provisionamento de dados sem toque
os dispositivos registrados, eles também podem concluir essas tarefas no EMM
no console do Google Cloud.
[null,null,["Última atualização 2025-08-29 UTC."],[[["\u003cp\u003eThe Common Android Reseller Library is a Java library that provides a unified integration for both Samsung's Knox Deployment Program (KDP) and Google's zero-touch enrollment services.\u003c/p\u003e\n"],["\u003cp\u003eThis library simplifies the process for device resellers to manage Samsung and other Android devices, allowing them to use a single set of tools for device assignment.\u003c/p\u003e\n"],["\u003cp\u003eResellers can use factory classes in the library, utilizing service account keys from Samsung's Knox Cloud API portal and Google's API Console, to perform actions like assigning devices to customers.\u003c/p\u003e\n"],["\u003cp\u003eCustomers who receive devices through this library can then use the Knox Mobile Enrollment (KME) portal for Samsung devices and the zero-touch enrollment portal for other Android devices to configure their newly acquired devices.\u003c/p\u003e\n"],["\u003cp\u003eThe library is primarily intended for device resellers who have yet to integrate with either zero-touch enrollment or KDP, providing a single point of integration for both.\u003c/p\u003e\n"]]],["The Common Android Reseller Library, a Java library, provides a unified approach for resellers to manage device enrollment for both Samsung and other Android devices. It uses factory classes and service account keys to interface with Samsung Knox and Google's zero-touch APIs. Resellers can create customer IDs and assign devices to customers via `ResellerService` objects and a common set of methods. Customers then utilize Knox Mobile Enrollment or the zero-touch portal to configure assigned devices.\n"],null,["# How it works\n\nThe Common Android Reseller Library is a Java library that interacts with the Samsung\nKnox APIs and the zero-touch [Reseller API](/zero-touch/guides/how-it-works) to\nprovide a single integration for Samsung's [Knox Deployment Program](https://www.samsungknox.com/en/knox-deployment-program)\n(KDP) and Google's zero-touch enrollment services.\n\n[KDP](https://www.samsungknox.com/en/knox-deployment-program) enables trusted\ndevice resellers to verify Samsung devices for their enterprise customers using\n[Knox Mobile Enrollment](https://www.samsungknox.com/en/solutions/it-solutions/knox-mobile-enrollment)\n(KME). Similarly, zero-touch enrollment allows enterprise customers to verify and\nconfigure [other Android devices](/zero-touch/resources/manufacturer-names)\npurchased from authorized device resellers.\nEnroll Samsung and other Android devices through a single integration.\n\nThe reseller library contains [two factory classes](/zero-touch/reseller-library/reference/factory-classes)---one\nfor each enrollment service. These factory classes accept service account\nkeys generated from Samsung's Knox Cloud API portal and Google's API Console to\nauthorize calls to Knox and zero-touch reseller APIs (for more details, see [Get started](/zero-touch/guides/reseller-library/get-started)).\nYou use these factory classes to [create `ResellerService` objects](/zero-touch/guides/reseller-library/common-operations#create_resellerservice_objects).\n\nA [common set of methods](/zero-touch/reseller-library/reference/methods) is\navailable to `ResellerService` objects that allow resellers to perform tasks\nsuch as assigning and unassigning devices to and from customers.\n\nAfter a reseller uses the library to assign devices to an enterprise customer,\nthe customer can use the KME portal to create and apply configs for Samsung\ndevices, and the zero-touch enrollment portal to create and apply configs for\nother Android devices.\n\nWho it's for\n------------\n\nThe Common Android Reseller Library is intended for device resellers that haven't\nintegrated with either zero-touch enrollment or [KDP](https://www.samsungknox.com/en/knox-deployment-program).\n\n- Resellers already integrated with zero-touch enrollment should integrate with [KDP](https://www.samsungknox.com/en/knox-deployment-program) separately to manage Samsung devices.\n- Resellers already integrated with [KDP](https://www.samsungknox.com/en/knox-deployment-program) should use zero-touch's [Reseller API](/zero-touch/guides/how-it-works) to manage non-Samsung devices.\n\n*** ** * ** ***\n\nExample workflow\n----------------\n\nBelow is an example workflow of how a reseller might use the client library\nto manage [KDP](https://www.samsungknox.com/en/knox-deployment-program) and\nzero-touch device enrollments. Code samples for performing basic tasks are\navailable in [Get started](/zero-touch/guides/reseller-library/get-started)\nand [Common operations](/zero-touch/guides/reseller-library/common-operations).\n\n### Receive purchase order\n\n1. An enterprise customer sends you a purchase order. The purchase order contains Samsung and [other Android devices](/zero-touch/resources/manufacturer-names).\n\n### Create customer IDs\n\n2. If this is a new customer, use the library to:\n 1. Create the customer's [zero-touch account](/zero-touch/guides/reseller-library/common-operations#other_android_devices_2).\n 2. Create the customer's [Samsung Knox Customer ID](/zero-touch/guides/reseller-library/common-operations#samsung_devices_2).\n3. If this is an existing customer (the customer already has zero-touch enrollment and Samsung Knox Customer IDs), then continue to Step 4.\n\n### Assign devices\n\n4. Use the reseller library to [assign\n devices to the customer](/zero-touch/guides/reseller-library/common-operations#claim_a_batch_of_devices), based on the customer's purchase order.\n\n### Create and apply device configs\n\n5. Customers can now create configs and apply them to their devices.\n 1. Samsung devices: customers use the [Knox Mobile Enrollment](https://docs.samsungknox.com/KME-Getting-Started/Content/about-kme.htm#h2_3) (KME) portal to create configs and apply them to the Samsung devices they were assigned in Step 4.\n 2. Other Android devices: customers use the [Zero-touch portal](https://support.google.com/work/android/answer/7514005#devices) to create configs and apply them to the non-Samsung devices they were assigned in Step 4. If the customer's EMM supports provisioning zero-touch enrollment devices, they can also complete these tasks in their EMM console.\n\n*** ** * ** ***\n\n**Next steps:** [Get started](/zero-touch/guides/reseller-library/get-started)"]]
