Unable to login to Container Management Portal at using vic appliance ip
Article ID: 327268
Updated On:
Products
Issue/Introduction
This article provides information why DNS is required for VIC Environment
Symptoms:
When connecting to the Container Management Portal at https://VIC-APPLIANCE-IP:8282.
Getting error :
"message":"SsoManager has not been initialized","statusCode":500,"documentKind":"com:vmware:xenon:common:ServiceErrorResponse","errorCode":0}
xenonHost Log Snippets:
[352][W][2018-07-03T06:47:43.388Z][40][8282/core/authn/basic][handleTokenVerify][Error verifying token: Separator for header not found]
[353][W][2018-07-03T06:47:43.388Z][40][8282/][lambda$verifyTokenInternal$38][Error verifying token: com.vmware.xenon.common.jwt.Verifier$InvalidTokenException: Separator for header not found]
[349][W][2018-07-03T06:47:43.387Z][18][8282/][lambda$verifyTokenInternal$38][Error verifying token: java.lang.IllegalStateException: SsoManager has not been initialized]
[354][I][2018-07-03T06:47:43.390Z][18][8282/][lambda$verifyTokenInternal$38][Retrying token verification with basic auth.]
[355][W][2018-07-03T06:47:43.390Z][18][8282/core/authn/basic][handleTokenVerify][Error verifying token: Separator for header not found]
[356][W][2018-07-03T06:47:43.391Z][18][8282/][lambda$verifyTokenInternal$38][Error verifying token: com.vmware.xenon.common.jwt.Verifier$InvalidTokenException: Separator for header not found]
[357][I][2018-07-03T06:47:59.450Z][22][8282/][lambda$schedulePeriodicCertificatesReload$1][Host https://192.168.63.179:8282/: reloading all certificates]
[358][I][2018-07-03T06:48:59.457Z][12][8282/][lambda$schedulePeriodicCertificatesReload$1][Host https://192.168.63.179:8282/: reloading all certificates]
[359][I][2018-07-03T06:49:59.458Z][12][8282/][lambda$schedulePeriodicCertificatesReload$1][Host https://192.168.63.179:8282/: reloading all certificates]
[360][I][2018-07-03T06:50:59.459Z][22][8282/][lambda$schedulePeriodicCertificatesReload$1][Host https://192.168.63.179:8282/: reloading all certificates]
[361][W][2018-07-03T06:51:28.194Z][62][8282/auth/psc/callback][redirectToSamlSso][Could not generate redirect URL: java.lang.IllegalStateException: SsoManager has not been initialized
at com.vmware.admiral.auth.idm.psc.saml.util.SamlManager.getInstance(SamlManager.java:100)
at com.vmware.admiral.auth.idm.psc.saml.sso.authentication.SamlRequestSender.<init>(SamlRequestSender.java:45)
at com.vmware.admiral.auth.idm.psc.saml.util.SsoUriGenerator.generateRedirectUrl(SsoUriGenerator.java:47)
at com.vmware.admiral.auth.idm.psc.service.PscAuthenticationService.redirectToSamlSso(PscAuthenticationService.java:498)
at com.vmware.admiral.auth.idm.psc.service.PscAuthenticationService.redirectToSso(PscAuthenticationService.java:491)
at com.vmware.admiral.auth.idm.psc.service.PscAuthenticationService.handleGet(PscAuthenticationService.java:474)
at com.vmware.xenon.common.StatelessService.handleRequest(StatelessService.java:120)
at com.vmware.xenon.common.StatelessService.handleRequest(StatelessService.java:103)
at com.vmware.xenon.common.ServiceHost.lambda$queueOrScheduleRequestInternal$45(ServiceHost.java:4301)
at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1402)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware vSphere Integrated Containers 1.x
Cause
- DNS is not setup at all or DNS is not setup correctly.
- VC details (hostname & IP address) are defined under host file of VIC appliance.
Resolution
- DNS should be configured correctly for VIC appliance.
- SSL completely depends on DNS.
- No DNS causes multiple issues between VIC appliance & PSC due to expecting FQDN for SAML tokens.
Feedback
