Overview 


Initially, the Suprema G-SDK used the Authentication API to configure operators. However, this method was limited to setting up only 10 operators.


Auth API: https://supremainc.github.io/g-sdk/api/auth/#config


To address this limitation, the Operator API, detailed below, was developed.

1. Operator API

To support a larger number of operators, a Operator API is included in the Suprema G-SDK. This API allows you to configure up to 1,000 operators.

The documentation for this Operator API states:

"Sets all device operators. When using AuthConfig, there is a limitation that you can set operators up to 10. Operator allows you to create and manage up to 1000 operators."


Suprema G-SDK Documentation: https://supremainc.github.io/g-sdk/api/operator/

2. Important Considerations When Using the Operator API


However, there are a few points to be aware of when utilizing the new Operator API. This article covers the precautions and important details regarding its use.


When Using the Operator API


When you start using the Operator API, any operators previously configured using the Auth API will be automatically migrated.

However, this migration process occurs only once. After this initial migration, if you attempt to configure operators using the Auth API again, that configuration will not take effect.


Therefore, we strongly advise that you use only the Operator API for management once you have started using it.

In other words, once the Operator API is in use, the operator values configured through Auth Config become invalid.



Note!
When retrieving operators using the Authentication API (e.g., for viewing or debugging), you might still see the old data. This data is meaningless after the initial migration to the Operator API.
Please ensure that all operator management—including creation, modification, and deletion—is strictly performed via the Operator API. Using the Authentication API for management after migration will not work.


For better comprehension, please refer to the diagram below.:



Notice!

We occasionally receive inquiries from customers who attempt to retrieve operators using the Auth API and report that operator functionality is not working correctly.
If your source code is internally configuring operators via the Auth API, please review and migrate to using the Operator API.