Hello!
At me it is established Sun Communication Express on 8080 port, and Sun Express Messanger on 80 port of my server. Authorization of the user on 80 port passes normally and with 8080 throws on authorization on 80 port, i.e. there is a double authorization. How to solve this problem?
In advance thanks!
Hi,
As Gary correctly indicated, this appears to be an issue with your sign-sign on settings.
Are you using messaging SSO?
What version of messaging server/uwc are you running?
If you are using messaging SSO, what have you set for the following:
configutil -o local.sso.uwc.verifyurl
configutil -o local.webmail.sso.cookiedomain
configutil -o local.webmail.sso.enable
configutil -o local.webmail.sso.id
configutil -o local.webmail.sso.ims.verifyurl
configutil -o local.webmail.sso.prefix
configutil -o local.webmail.sso.singlesignoff
configutil -o local.webmail.sso.uwccontexturi
configutil -o local.webmail.sso.uwcenabled
configutil -o local.webmail.sso.uwclogouturl
configutil -o local.webmail.sso.uwcport
and what are the following settings in uwcauth.properties set to:
uwcauth.sessioncookie
uwcauth.appprefix
messagingsso.appid
uwcauth.cookiedomain
uwcauth.messagingsso.enable
uwcauth.messagingsso.cookiepath
messagingsso.ims.url
messagingsso.uwc.url
uwcauth.appid
Shane.
Versions of the products established at me:
Sun Java(tm) System Messenger Express 6.2
Sun Java System Communications Express 6 2005Q4
My variables:
./configutil | grep sso
131:local.webmail.sso.amcookiename = iPlanetDirectoryPro
132:local.webmail.sso.amnamingurl = http://my.domain.com:8080/amserver/namingservice
133:local.webmail.sso.enable = 0
134:local.webmail.sso.singlesignoff = 1
135:local.webmail.sso.uwccontexturi = webmail
136:local.webmail.sso.uwcenabled = 1
137:local.webmail.sso.uwclogouturl = http://my.domain.com:8080/webmail/base/UWCmain?op=logout
138:local.webmail.sso.uwcport = 8080
./configutil | grep uws
local.webmail.uwcrppsupport = 0
Tell what else variable it is necessary to use and with what parameters?
Hi,
Based on the information you provided it appears you are using access manager for single sign-on (and not messaging server). Therefore a lot of the parameters I provided don't apply.
Your best best is to go through the "Setting up Access Manager Single Sign-On" section of the 2005Q4 Comms Express Admin Guide step by step and double-check all your values (especially things like port numbers).
Shane.
Thanks.
But I need how to use not clearly Communication Express on 80 port, in fact on it hangs Message Express? And I so have understood that one without another will not work?
Excuse me for silly questions I can not simply understand in any way, and with English at me it is bad: (
I'm not really sure what your first queston means, soory...
Communication Express (also known as UWC) runs on a web server, and communicates with "Messaging Express", our old webmail product.
If they're both on the same system, they must run on different ports, or on different ip addresses.
Does this answer you?
>>Communication Express (also known as UWC) runs on a web server, and
>>communicates with "Messaging Express", our old webmail product.
>>If they're both on the same system, they must run on different ports, or on
>>different ip addresses.
Ok. But for what then at installation UWC the fitter asks on what to port me hangs Express Messanger?
To me the technology is simply a little not clear, therefore I likely and cannot understand :)
Hi,
By default Messenger Express listens on port 80. If you want Communication Express (UWC) to also run on port 80 you can simply change the Messenger Express port by doing the following (in the messaging server sbin directory):
./configutil -o service.http.port -v 1080
./stop-msg http
./start-msg http
Now you should be able to connect to the old messenger express interface on port 1080 i.e.
http://<email host>:1080/
If that works, then you can install UWC, and when it asks for the Messenger Express port, use 1080 instead of 80.
Regards,
Shane.
I'll try to explain how CE works with ME
1. ME (the old webmail product) is required for CE to work. It continues to work by itself, in that you can point a browser to the port where ME is running, and log in, and see your mail.
by default, ME installs to port 80, but you can change it.
2. CE communicates to ME, not to the store itself. That means that CE cannot be installed on the same port/ip on the same machine as ME. It can be installed on another port, so
when you connect to CE, CE gets your mail from ME
Is that more clear, now?
