Cisco Cisco Elastic Services Controller 2.3 Developer's Guide
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
01-Tenants : Manage ESC tenants
where YWRtaW46Y2lzY28xMjM= is the Base64 enconded string of the default username/password
(admin:cisco123)
(admin:cisco123)
Most libraries and web clients have an interface for simply providing the username/password and the app
will encode the username/password and add the HTTP Basic Auth header.
will encode the username/password and add the HTTP Basic Auth header.
Example using the default admin/cisco123 credentials:
http://[ESCVM_IP]:8080/ESCManager/v0/tenants/
Headers:
Content-Type application/xml
Authorization Basic YWRtaW46Y2lzY28xMjM=
Content-Type application/xml
Authorization Basic YWRtaW46Y2lzY28xMjM=
REST Https Support
Overview
ESC supports https communication over port 8443. ESC will generate a self-signed certificate that the client
will need to trust to get the https communication going.
will need to trust to get the https communication going.
Setup
By default, the REST https is disabled and restricted to localhost. To enable it pass the argument --enable-
https-rest to ESC bootvm.py, ESC installation script.
https-rest to ESC bootvm.py, ESC installation script.
HA Considerations
In an HA setup every ESC HA VM will have its own self-signed generated certificate. Upon an HA
switchover, ESC north bound client will be required to re-accept the new certificate it will be served.
switchover, ESC north bound client will be required to re-accept the new certificate it will be served.
REST API List
Implementation Notes
All tenants in ESC will be returned as a List
Response Class (Status 200)
[
{
"internal_tenant_id":
{
"internal_tenant_id":
"string"
,