Hi Rajesh:
As I wrote earlier in this thread, X.509 would the most “correct” solution. But your solution is quite an innovative.
Some suggestions: to avoid storing the username and password on the user’s machine, one can associate a random cookie with the username and password on the server(perhaps using the repo). This could then be looked up when the cookie is presented, and then the auto login can be completed. Storing the password in cleartext in the repo is still a hack but is required since there is no easy way to retrive the user’s password on the server. At least the credentials get on the server side now.
Also, it should be possible to avoid Tomcat… the archives should have a Java snippet that sends back arbitrary HTTP response headers – you can use it to send a Set-Cookie header. The service pub.flow:getTransportInfo will let you read the cookie headers from Flow.
Example cookies:
#response HTTP header used to set cookie on client
Set-Cookie: mycookie=random123; path=/;
#Subsequent client request header containing cookie
Cookie: mycookie=random123
#webmethods-Protocol-and-Transport#Integration-Server-and-ESB#webMethods