Hi Pablo, I've been testing and I could not reproduce the issue right now, but it happened to me once if I remember well. The script that generates the 'idm2chanchan.json' was not able to access the database, which could cause the issue. Probably is a timing issue due to the synchronization of all the containers. We will have a look at it. Still, if you remove the containers and try to generate them again, probably you will be able to run tourguide normally (if you are working with volumes you should not lose any changes). Sorry for the inconvenience! Best, Alberto Martín On Fri, Feb 5, 2016 at 11:57 AM, Pablo Fernández Moniz < pablofernandezmoniz at gmail.com> wrote: > Hello, > > we are working to introduce the changes related to occupancy levels and > reviews identifiers and we have found that we cannot log in on the app > using IdM after retrieving the last modifications [idm_error.tiff]. We > think that it occurs because the url and the callback url are set to > localhost instead of the tourguide host [idm_localhost.tiff]. > > During installation we noticed that the tourguide_1 failed to retrieve the > file '/config/idm2chanchan.json' [failed_to_retrieve_idm2chanchan.json.tiff] > > We don't discard that the issue is related to the refactoring process but > we have revised our code and didn't find evidences of it. We have pushed > our code to the branch fix/client_login_idm so you can reproduce the error > by yourself. > > Do you have any suggestion about what is causing this error? > > > Regards, > > FIWARE ULPGC team. > > _______________________________________________ > Fiware-developer-experience mailing list > Fiware-developer-experience at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-developer-experience > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20160208/6872e1ad/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy