Closed AnotherCodeArtist closed 8 years ago
After checking your source code I figured out how the request URL is constructed and I ended up with the following configuration:
# ACCESS CONTROL GE
ACCESS_CONTROL_URL = 'http://10.12.200.247:8282'
ACCESS_CONTROL_MAGIC_KEY = 'undefined'
Nevertheless an erroneous URL should not cause the application to fail and I'm now facing a different problem leading to new issue
Hi, thanks for the update. Could we close the issue?
Well, if it's ok for you that the application crashes rather than providing a decent error handling, than you can close this one and probably focus on that one ;-)?
Hello @AnotherCodeArtist
We'll do our best to include a better error handling in case of a configuration issue with AZF in a future release of KeyRock, so that this issue is not repetead again.
I'll close the issue now if it's ok with you, but will let you know when this enhancement is included. Hope you're still interested by then :smile:
Thanks again for your contribution.
Hi!
Just allow me one question upfront: Do you really believe that anyone can manage to setup the interaction between IdM and AZF based on this documentation?
Anyway, I'm struggling with the configuration for some time now, and after reading some of your issue threads (e.g.: https://github.com/ging/fiware-idm/issues/49) I did the following:
When checking this URL I get the following response:
So whenever I save the application, I get the following error (container log):
The django web app also comes up with an impressive error dump:
So what's wrong here? At least I would not expect the web-app to completely crash if there's something wrong with the configuration. An if there is something wrong with the configuration, a more verbose documentation might help?
So any help is highly appreciated, since I'm evaluating the FIWARE stack for a customer.