h1. Why
The core team is working on adding support for DMZ, it means that developers can setup a proxy url for a given service.
However, they are having a problem that different services are using different URLs in the configuration file. For example, the auth sdks are using the "auth-server-url" field in the "config" field in the keycloak configuration object, rather than the "url" field.
After discussion with other service team and the core team, we have decided all the services should use the "url" field in the configuration. This will make it easier to core team to update the the right url field (they don't need to have different logic for different service to find the right url field to update), and keep it consistent across all the SDKs of all the services.
h2. What
At the moment, the configuration of keycloak service looks like this:
{ quote} {
{
"id": "keycloak",
"name": "keycloak",
"type": "keycloak",
"url": "https://keycloak.security.feedhenry.org",
"config": {
"auth-server-url": "https://keycloak.security.feedhenry.org/auth",
"realm": "secure-app",
"resource": "client-app",
"ssl-required": "external",
"url": "https://keycloak.security.feedhenry.org/auth"
}
} ,{quote
} }
and in the auth SDKs in all the platforms, the `config.auth-server-url` field is being used to build the full url for keycloak.
We should change it in all the SDKs (ios, android, cordova, xamarin) to just use the "url" field instead.
ping [~craig.brookes] [~davidmartin] FYI.
|
|
