• Post Reply Bookmark Topic Watch Topic
  • New Topic

cross-server login  RSS feed

 
Shashidhar Yarabati
Ranch Hand
Posts: 175
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All!
I have got a question when I was attended for interview this weak. The solution for this I don't know. If you come across please help me to learn.
The Question is:
I have a Logup page(Logup.jsp). In that I have some fields(say fname,mname etc..,) to register in Site A which is using WEBLOGIC server, And I have a chech box mentioning: Register in Site B along with Site A in the same Logup.jsp page. But the Site B is using different Server say TOMCAT. Now if the user checks the box then we have to register him for Site A(WEBLOGIC server) and Site B(TOMCAT). Other wise for only Site A(WEBLOGIC).
Now the question is how to transfer my control after creating the user account in WEBLOGIC server(Site A) to create account in TOMCAT(Site B). First of all is it possible???
If Yes How is it???
Which API/Class should we use for this???

Thank's in Advance.

Sashi
SCJP1.5
[ June 21, 2007: Message edited by: Bear Bibeault ]
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 66144
144
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please use a meaningful subject line for your posts. I have adjusted this one for you.

Please read this for more information.
 
Anupam Sinha
Ranch Hand
Posts: 1090
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It shouldn't really matter if it's Weblogic or Tomcat or for that matter any web/application server. You would need to transfer all the info from site A to site B depending upon the checkbox. Initiate a request from your site A to site B with all the values like fname etc. You would need to place in checks if the username in site A is available in site B if not then who handles such a scenario and other such stuff.
 
Ulf Dittmer
Rancher
Posts: 42972
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on what SiteA and SiteB are. If they're hosted on www.company.com and xyz.company.com, then a session cookie can be set for "company.com". That would then be used by both, and as long as all user information was accessible to both sites -say, in database both servers have access to- there'd be no problem implementing this.

You wouldn't even need a cookie (and thus the sites wouldn't both need to be "....company.com") if separate logins are acceptable, as long as the servers can access the user information in a shared repository.
[ June 21, 2007: Message edited by: Ulf Dittmer ]
 
Shashidhar Yarabati
Ranch Hand
Posts: 175
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's typing mistake
Iam sorry for the subject line
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!