Skip to content
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.

Authentication problem on web-admin #31

Closed
borisbaldassari opened this issue Dec 22, 2018 · 8 comments
Closed

Authentication problem on web-admin #31

borisbaldassari opened this issue Dec 22, 2018 · 8 comments
Assignees

Comments

@borisbaldassari
Copy link
Member

On ci4 I re-pulled and re-built everything, pruned everything I could, and I still have the failed auth issue in the web admin part. As indicated in the readme I've updated the web-admin Dockerfile:

ENV API_GATEWAY_VAR=http://ci4.castalia.camp:8086

I checked that port 8086 is the one provided by the api-server service.
Please not it is not a up/down/up issue since this is the first run of these containers. Also, the fix provided for that error by @MarcioMateus worked for me before the recent changes.

@borisbaldassari
Copy link
Member Author

After launching the docker images, one has to wait for some time before trying to log in the admin webapp, the time for the corresponding docker image to finish its initialisation. This time needs to be estimated and documented.

@mhow2
Copy link
Contributor

mhow2 commented Feb 25, 2019

Or consider others options :

  • a kind of "waiting for auth service to come up" message within the admin-UI.
  • make the admin-webapp container to wait for the complete auth-server availability before starting up.

@borisbaldassari
Copy link
Member Author

borisbaldassari commented Mar 7, 2019

@davidediruscio Would you have any recommendation regarding Martin's proposal? Should we simply update the doc (stating an unknown delay), display a message or make the container wait?

@davidediruscio
Copy link

davidediruscio commented Mar 7, 2019 via email

@davidediruscio
Copy link

davidediruscio commented Mar 7, 2019 via email

@ambpro
Copy link
Contributor

ambpro commented Mar 8, 2019

@davidediruscio , I think so. In this context, we can perform this checking in the admin-ui level or we can also work around the problem using a waiting-script for the oss-db when it will be really ready in the docker-compose level.
I 'll take a look on it asap.

@mhow2
Copy link
Contributor

mhow2 commented Mar 25, 2019

hi @ambpro : is there any news about it ?

@borisbaldassari
Copy link
Member Author

Is fixed, thanks @ambpro

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants