BAETYL 0.1.6 Documentationaddress is tcp://127.0.0.1:50050. At present, the authentication mode of the interface adopts a simple dynamic token. When the Master starts the services, it will dynamically generate a Token for each service header. It should be noted that the dynamically launched instance cannot obtain the Token, so the dynamic instance cannot dynamically start other instances. For the service instance, after the instance Header key is as follows: • x-openedge-username: service name as username • x-openedge-password: dynamic token as password The following are the currently available interfaces: • GET /v1/system/inspect0 码力 | 120 页 | 7.27 MB | 1 年前3
BAETYL 0.1.6 Documentationaddress is tcp://127.0.0.1:50050. At present, the authentication mode of the interface adopts a simple dynamic token. When the Master starts the services, it will dynamically generate a Token for each service header. It should be noted that the dynamically launched instance cannot obtain the Token, so the dynamic instance cannot dynamically start other instances. For the service instance, after the instance The Header key is as follows: x-openedge-username: service name as username x-openedge-password: dynamic token as password The following are the currently available interfaces: GET /v1/system/inspect0 码力 | 119 页 | 11.46 MB | 1 年前3
BAETYL 1.0.0 Documentationaddress is tcp://127.0.0.1:50050. At present, the authentication mode of the interface adopts a simple dynamic token. When the Master starts the services, it will dynamically generate a Token for each service header. It should be noted that the dynamically launched instance cannot obtain the Token, so the dynamic instance cannot dynamically start other instances. For the service instance, after the instance The Header key is as follows: x-openedge-username: service name as username x-openedge-password: dynamic token as password The following are the currently available interfaces: GET /v1/system/inspect0 码力 | 135 页 | 15.44 MB | 1 年前3
BAETYL 1.0.0 Documentationaddress is tcp://127.0.0.1:50050. At present, the authentication mode of the interface adopts a simple dynamic token. When the Master starts the services, it will dynamically generate a Token for each service header. It should be noted that the dynamically launched instance cannot obtain the Token, so the dynamic instance cannot dynamically start other instances. For the service instance, after the instance Header key is as follows: • x-openedge-username: service name as username • x-openedge-password: dynamic token as password The following are the currently available interfaces: • GET /v1/system/inspect0 码力 | 145 页 | 9.31 MB | 1 年前3
共 4 条
- 1













