Uwc redirect w/ POST /uwc/wabp/login.wabp cmd & uwcauth.admins=calmaster

Question

We enabled uwcauth.admins and restarted the web container in SCS6U1. Now instead of getting proxyauth being disallowed we get redirected after a successful proxy authentication. The web client fails because of this redirection instead of accessing the wabp functions. Proxyauth appears to work with iwc/svc and it doesn't redirect us but we're not sure if NotifyLink is compatible with iwc as it also doesn't work. When the redirection takes place we aren't sent to a new hostname or port. It strips the path and redirects to /uwc for the same hostname and port we initially connected to. We are not using SSO and it doesn't seem to matter what the uwcauth.ssl.enabled paramter is active or whether we use SSL to access the site. Why is this redirection happening and what if anything can we change to stop it?
POST /uwc/wabp/login.wabp HTTP/1.1
Content-Type: application/x-www-form-urlencoded
User-Agent: NotifyLink Enterprise Server
Host: servername.domain
Content-Length: 71
Connection: Keep-Alive
&username=calmaster&password=password&authOnly=true&proxyauth=username
HTTP/1.1 302 Moved Temporarily
X-Powered-By: Servlet/2.5
Server: Sun Java System Application Server 9.1_02
Set-Cookie: JSESSIONID=b923cd21e6b1c033b10ed679d4bc; Path=/uwc
Cache-Control: private
Location: http://servername.domain/uwc/
Content-Type: text/html; charset=iso-8859-1
Content-Length: 0
Date: Thu, 07 May 2009 14:55:17 GMT
GET /uwc/ HTTP/1.1
User-Agent: NotifyLink Enterprise Server
Host: servername.domain
Connection: Keep-Alive
Cookie: JSESSIONID=b923cd21e6b1c033b10ed679d4bc
HTTP/1.1 200 OK
X-Powered-By: JSP/2.1
Server: Sun Java System Application Server 9.1_02
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 54
Date: Thu, 07 May 2009 14:55:17 GMT

Answer 1

We tried looking at the uwc log file and I saw a Stack trace at one point but couldn't really determine anything from it. I found a workaround that works for me, but I consider it somewhat of a hack. It doesn't seem like I should need to do this, yet it makes it closer to a 'single host install' demo config. I encountered the problem because I am always trying to minimize the complexity of any installs I do by trimming out support for things which I do not want or need. We do not use the mail server portion of SCS6 thus long ago I removed most of the mail software components and support for mail (except for smtp event reminders to another mail host) and setup the domain and users with only -S cal (not mail or im). Since wabp logins work fine in iwc but iwc isn't compatible with NotifyLink (yet?), we couldn't use that, and it hints to me that uwc is more strict about the domain/users setup.
All of these steps are required (modify usernames, passwords, domains as necessary to match your needs)
Add mail service to the domain: (I doubt the mail hostname needs to be correct if we don't use mail, but it is required to be listed)
/opt/sun/comms/da/bin/commadmin domain modify -D admin -w adminpass -n domain.name -d domain.name -S mail -H
mailhost.for.domain.name
Then for every user that needs proxy auth to work with wabp through uwc:
/opt/sun/comms/da/bin/commadmin user modify -D admin -n domain.name -w adminpass -l username -S mail
Redeploy uwc with mail support, bogus server values for the mail portion is okay since we wont use it, ignore the can't connect to mail server warning since its bogus anyway.
Remember to re-enable proxy auth in /var/opt/sun/comms/ce/WEB-INF/config/uwcauth.properties
and any other uwc settings that got wiped out by the re-deploy.
Restart the application container server.
I noticed another thread mentioning this one, so I will mention this post over there.