William wrote:
The situation is that we have a lot of legacy users who only enter a username, without realm information, and passwords for their connections. Those work fine. When newer users enter username@realm for their password I need to strip off the realm, and authenticate that user.
In 2.0, add the following to proxy.conf: realm example.com { } Once that's done, the default configuration in 2.0 will treat "user@example.com" the same as "user". See the debug output, where it shows it stripping the realm.
Our old system used the strip directive to do this. I cannot figure out how 2.0 does this. The problem becomes that if they put a different realm on the username, we will need to either proxy it (later configuration issue, not for now) or reject it.
Later, add a home server configuration to the realm, and it will be proxied. Alan DeKok.