127.0.0.1 [17/Sep/2015:14:38:09 +0200][95657 ms] "GET /identity/api/tenants/dev/principals/?role=COM_VMWARE_IAAS_IAAS_ADMINISTRATOR HTTP/1.1" 200 1274 [tomcat-http--25]127.0.0.1 [17/Sep/2015:14:38:14 +0200][101086 ms] "GET /identity/api/tenants/dev/principals/?role=CSP_TENANT_ADMIN HTTP/1.1" 200 1274 [tomcat-http--32]127.0.0.1 [17/Sep/2015:14:38:29 +0200][115729 ms] "GET /identity/api/tenants/dev/groups/?role=COM_VMWARE_IAAS_IAAS_ADMINISTRATOR HTTP/1.1" 200 302 [tomcat-http--50]127.0.0.1 [17/Sep/2015:14:38:34 +0200][121182 ms] "GET /identity/api/tenants/dev/groups/?role=CSP_TENANT_ADMIN HTTP/1.1" 200 306 [tomcat-http--43]
To work around this issue, increase the shindig timeout setting:
Note: Before making any changes, make a backup of the shindig.properties file.
Note: Increasing the time-out as described is a short-term workaround in order to successfully load the admin page again. Adding more admins later, or having a slow network connection may expose the same problem again.
For best practice, if possible, VMware recommends to combine the admins in an AD group and assign the group to the corresponding roles for the long term solution.
<?xml:namespace prefix = "o" />