Closed bcollard closed 7 years ago
Hello @bcollard,
There is no more local registry
since the first official version of Gravitee.io AM.
Local registry was introduced because of a lack of UI to manage security domains at the very beginning of the project.
So the best option for you is to migrate
your previous domain definition (json) into a domain managed by the gateway itself (using the UI or by invoking the Rest API).
Is this response ok for you ?
Issue has been moved to: https://github.com/gravitee-io/graviteeio-access-management/issues/78
Ok, indeed it does not work neither with version 1.0, nor version 1.1.
If you have a look into /plugins directory, you will that there is no local-registry
plugin.
It must not work for both 1.0 and 1.1 and also for next versions. There is absolutely no reason to maintain this kind of plugins now that there is a management UI.
You were able to use it because you were running an unofficial version and not yet released version of AM.
Actually, what led us to this point is that the Domain menu does not load. See below:
Each time we click the Domain menu, it finishes with timeout. In the gateway logs, we can see that:
Gateway JVM is configured with HTTP proxy to reach the Internet.
Please ask your question at the right place, this issue has been moved to https://github.com/gravitee-io/graviteeio-access-management/issues/78
Hi,
We have a domain configured into the /domains dir. This json file is not loaded at gateway startup.
Only the "default" domain "admin" is shown in logs and is stored in the Management repository (MongoDB DS).
Part of the configuration is below:
I can send the custom domain conf privately.
Am I missing something?