In order to be able to reverse engineer the behavior of SSO / New Edge UI config for private cloud, I need to enable deep debugging in the Apigee internals of setup.sh and apigee-service, in order to determine how public / non-public hosts / ports get replaced in all the Apigee internal config files.
Is there any generic swith to configure, e.g. in customer properties or in the Apigee config files, to massively increase the log level to tracing?
The documentation is quite incomplete / inconsistent, and i am not able to costruct of host/IP/port combinations based on the tiny incomplete documentation snippets provided by Apigee.
Due to complexity, we need to set up everything in one shot, otherwise config of Apigee gets even more complex:
- SSO with IdP
- New Edge UI
- TLS for MS / New Edge UI / SSO
- Load balancers (non-terminating), having standard HTTPs ports 443, in contrast to components having some custom ports (need to modify all of them in order to be able to test due to company firewall restrictions.
In our test environment, we're using 4.50.00.08 in on-premise, with a global 49 node setup across 9 data centers, in 5 different network zones separated by firewalls.
I am already struggling since 7 days, trying different permutations of using LB DNS alias, replacing IP with host or DNS alias, reverse-engineering Java / SpringBoot libraries used by Apigee based on the errors observed in the log, reverse engineering placeholder replacements in the setup.
However, always ending up with inconsitent host/port combinations, sometimes empty host name, sometimes setup getting stuck during server restart.
I had to fully uninstall sso / ui including manual removal of non-deleted artifacts in e.g. tokens folder, somtimes had to kill -9 some orphaned processes.
I need at least a trace from the provided Apigee config file up to the files populated in the component's config folders, in order to see where something wrong was catched up or not refreshed or silently ignored.
LinkedIn
Twitter
