|
|
|
|
|
|
10/6/2017 5:12:55 PM
& more tests.
|
10/6/2017 1:28:43 PM
provide a configurable way for dynamic proxy route selection
for the default HttpClient based on regex based targetHostname patterns.
Introduced `ProxyMapping` to describe a regex based mapping
between target hosts and the proxy URL to use.
A `ProxyMapping` can be build from an ordered list of string based
mapping representations, e.g:
``` ^.*.(google.com|googleapis.com)$;http://localhost:8080
```
If the targetHost does not match a configured proxy mapping,
no proxy is used.
This can be configured via standalone.xml / jboss-cli, e.g.:
``` echo SETUP: Configure proxy routes for HttpClient SPI /subsystem=keycloak-server/spi=connectionsHttpClient/provider=default:add(enabled=true) /subsystem=keycloak-server/spi=connectionsHttpClient/provider=default:write-attribute(name=properties.proxy-mappings,value=["^.*.(google.com|googleapis.com)$;http://www-proxy1:8080","^.*.facebook.com$;http://www-proxy2:8080"])
```
The new `ProxyMappingWareRoutePlanner` uses a configured `ProxyMapping`
to decide which proxy to use for a given request based on the target host
denoted by the HTTP request to execute.
I verified this manually with the BurpProxy Suite.
|
1/24/2018 1:54:34 PM
OTP manual config pages
|
1/24/2018 2:45:24 PM
HOTP
|
1/11/2018 12:58:44 PM
escaping for the `totpStep1` message as it includes HTML links.
|
1/22/2018 6:57:50 AM
Response' switch to fix backwards compatibility with Keycloak 2.X adapters
|
11/15/2017 7:22:30 AM
original use case is to support imported credentials with a different key size without
implementing a totally new PasswordHashProvider
|
