Forum Discussion
Domino web access and Big-IP LTM - iRule question
Hello, I am looking into a way of replacing an ISA proxy server that is providing external access to an non clustered iNotes environment. Following the F5 deployment guide has not been successful as the iRule logic seems to be designed to load balance between multiple servers. (https://www.f5.com/pdf/deployment-guides/f5-ibm-inotes-dg.pdf)
I would appreciate if anybody can point me on the right track with ideas or references so I can write an iRule that can achieve the following scenario.
VIP vip.externaldomain.com - Front end to client on 443
Back end on port 80 domino1.internaldomain.com (Login and redirector) (mail.internaldomain.com) domino2.internaldomain.com (mail server) domino3.internaldomain.com (mail server)
As an example to show how this works for a user which has it's mailbox at domino2, the following is the flow that a client goes through
- Initial login at domino1 server (User goes to mail.internaldomain.com)
- POST user id and pwd to domino1
- GET from domino1 to go to domino2 and receive LTPA token (URL=http://domino2.internaldomain.com/mail/amailtes.nsf?OpenDatabase)
- GET to domino2 URL and send LTPA token (this shows the webmail gui)
I want to have a virtual server that can handle all this communication while the end user always sees one URL on the frontend, so I am thinking that the iRule needs to first always send the initial communication to domino1, catch or remember to which server the user was sent, and re-write all future communication to that server where it has it's mailbox, for that session, and also I assume the LTPA token needs to be stored at some point so the authentication to the mailbox server can work. Any thoughts???
Thanks so much!
Enrique R
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com