Hi all - any help with this will be greatly appreciated.
We are just starting to roll out Single Sign On in our Domino and WebSphere Environment, using LTPA.
Everything works fine, providing the URL used to access the Domino servers use the fully qualified domain name of the Domino server.
However, we are trying to incorporate SSO into an existing environment where people are currently used to simply using the host name of the server in their URL’s. Therefore we have users who will be using URL’s such as http://mailsvr1/mail/file.nsf
Obviously, this prevents the user from logging in as the server is part of the SSO “domain” and therefore even the correct user name and password are useless unless the full URL is used such as http://mailsvr1.domain.com/mail/file.nsf
Does anyone know any way of automatically changing any short URL’s to long URL’s? The rediret and substitute rules only seem to work on paths after the host or FQDN sadly.
I have been looking through support pages etc. From an app server perspective (where people are only typing in the short name of the server and nothing else on the URL, ie no paths to NSF or HTM files) I think we will be OK as we can set the fqdn and path to a homepage in the server document, so any navigation will keep the right structure, it’s more for the mail files and people’s existing bookmarks that I am worried about.