Hi,

we are trying to setup an wstore instance on FI-WARE Lab for weeks right now. Last week we finally found some regions, supplying sufficient resources of CPU, RAM, HDD, external IPs in one place and a working routing of the external ip address to the internal network.

We tried to run the Blueprint Templates in the regions Spain, Spain2, Berlin, Waterford, Crete, Budapest, Zurich, Trento and PiraeusU, but the deployment of the instance failed in every region because of missing external ips and/or an internal server error 500. The only working instance of the wstore we could manage was built on the wstore-image in PiraeusU. We are able to get the login page, but we could neither signup nor login. So we changed the wstore configuration in the settings.py as mentioned in https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Store_-_W-Store_-_Installation_and_Administration_Guide#FI-WARE_Identity_management to use the FI-WARE Lab Identity Manager Service and configured the application on https://account.lab.fiware.org/ .

Now the FI-WARE Identity Manager Service is used, but the wstore can't handle the authentication request, because the url /authorize is not found on the system:

Page not found (404)
Request Method: GET
Request URL: http://[instance-ip]/authorize?redirect_uri=http%3A%2F%2F[instance-ip]%2Fcomplete%2Ffiware%2F&response_type=code&client_id=[app-id]&next=/

So what is broken with the wstore image? We wanted to use the FI-WARE Lab for building our MVP. If we now have the setup our own cloud instance from scratch, the development of the MVP will be postponed to many days, so we hope for having a FI-WARE Lab instance of wstore up and running this week.

Please tell me where we could get help setting up a running wstore instance on the FI-WARE Lab cloud.

best regards,

Christian Kaspar

Christian Kaspar <christian@sponsoo.de>