Unassigned Hosts: Global Inventory List -> Hosts -> Unassigned HostsNetwork Pools: Global Inventory List -> Hosts -> Network Pools
Authorization Error : Unauthorized access.
There is a restriction with the page you are trying to reach and it cannot be displayed.
The same behavior can be observed in vCenter password management page failing to load the component passwords and instead displaying the following error: Failed to load password management data. Cannot convert a Symbol value to a string Failed to load PSC data.
Cannot convert a Symbol value to a string
vsphere_client_virgo.log highlights either of the below errors, where "sddcmgr.domain" is the SDDC Manager that should be looked into regarding this KB's issue./var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log
YYY-MM-DD] [WARN ] -nio-127.0.0.1-####-exec-### com.vmware.vsphere.client.rest.SsoTokenController Error pushing SAML token to web hook com.vmware.vcf.client:version.and.build:########## of plugin https://sddcmgr.domain:443/plugin/api/saml-hook; thumbprint=null; certificate=.
org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request: "<html><EOL><EOL><head><title>400 Request Header Or Cookie Too Large</title></head><EOL><EOL><body><EOL><EOL><center><h1>400 Bad Request</h1></center><EOL><EOL><center>Request Header Or Cookie Too Large</center><EOL><EOL><hr><center>nginx</center><EOL><EOL></body><EOL><EOL></html><EOL><EOL>"
YYYY-MM-DD7THH:MM:SS.sssZ WARNING vsphere-ui 330971 [vc@#### threadName="http-nio-127.0.0.1-####-exec-###" logger="com.vmware.vsphere.client.rest.SsoTokenController" ] Error pushing SAML token to web hook com.vmware.vcf.client:version.and.build:######
### of plugin https://sddcmgr.domain:443/plugin/api/saml-hook; thumbprint=null; certificate=-org.springframework.web.client.HttpServerErrorException$InternalServerError: 500 Internal Server Error on POST request for "https://sddcmgr.domain:443/plugin/api/saml-hook": [no body]VMware Cloud Foundation 9.0.x
VCF Operations 9.0.x
vCenter Server 9.0.x
The issue is encountered due to the SAML token length exceeding the default nginx buffer size configuration.
The issue is under Broadcom Engineering review and the fix is expected to be included in the future release.
Workaround:
cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.backup
client_header_buffer_size 4k;
large_client_header_buffers 4 32k;Reference:
Original File (before any changes):
http {
limit_conn_zone $server_name zone=per_server:10m;
limit_conn per_server 1000;
limit_conn_zone $binary_remote_addr zone=per_ip:10m;
limit_conn per_ip 100;
limit_req_zone $binary_remote_addr zone=api_traffic:10m rate=5000r/s;
limit_req_zone $binary_remote_addr zone=ui_traffic:10m rate=1000r/s;
limit_req_zone $binary_remote_addr zone=ui_file_upload:10m rate=1r/s;
map_hash_bucket_size 128;
proxy_send_timeout 600;
proxy_read_timeout 600;
Updated File (after the above changes):
http {
limit_conn_zone $server_name zone=per_server:10m;
limit_conn per_server 1000;
limit_conn_zone $binary_remote_addr zone=per_ip:10m;
limit_conn per_ip 100;
limit_req_zone $binary_remote_addr zone=api_traffic:10m rate=5000r/s;
limit_req_zone $binary_remote_addr zone=ui_traffic:10m rate=1000r/s;
limit_req_zone $binary_remote_addr zone=ui_file_upload:10m rate=1r/s;
map_hash_bucket_size 128;
client_header_buffer_size 4k;
large_client_header_buffers 4 32k;
proxy_send_timeout 600;
proxy_read_timeout 600;
nginx -s reload
If the issue persists: