ServerAlias? (was Re: [JDEV] Jabber 1.4: using IP instead of FQN)

[kadokev at msg.net]

There does not appear to be a jabber 'ServerAlias' function akin to Apache's?

Some background:
I'm building a dual-homed Jabber server on an extranet. The service should
appear to internal users as an internal server 'jabber.internal.mycorp'
(note that this is private DNS, not a .com), and also as 'jabber.mycorp.com'
for external users, AIM, etc.

My goal is to have internal users connect to 'jabber.internal.mycorp' for
purely internal communication, and when working from home or on the road,
still access their offline messages and use the same password by the public
name 'jabber.mycorp.com', over SSL.


Referring to an old discussion on this list:
> or, you should be able to put a <alias to="myhost.com"/> in the c2s
>configuration, to make any hostname, including "12.34.56.78" be mapped
>to "myhost.com".. NOTE, I do not know if this was ever thourougly tested,
>it would be interesting to see if it works correctly.. *g*

The construct '<alias to="myhost.com"/>' does not appear in jabber-1.4.

I do not see any reference to 'alias' as a legal statement in the c2s
configuration. This feature would solve my problem quite nicely, I'd be
willing to write the code if this is a feature the Jabber community desires.
 

>> Also keep in mind that the 'jabber.org' and '208.245.212.100' cannot be
>>the same thing within JSM - if one  person connected as test at 208.245.212.100,
>>they will be on a different virtual server than test at jabber.org.

That is the configuration I have now, with two host entries.

	<host>jabber.internal.mycorp</host>
	<host>jabber.mycorp.com></host>

The server maintains two virtual servers, with separate spool directories.
This means users registered in one virtual server do not exist on the other,
though they can communicate. This actually isn't a bad solution, particularly
if I implement external authentication so they can use the same password on
both sides, and maintaining contact lists is a problem.

If anybody else has implemented a similar design or would like assistance
in planning to deploy jabber in this manner, feel free to send email.

Kevin Kadow
MSG.Net, Inc.