|
Home > Archive > WebSphere Portal Server > July 2006 > Employee access to portal from outside of the network
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Employee access to portal from outside of the network
|
|
|
| Is there a best practise for determining whether a user is accessing a portal from within or outside of the network?
I work for a client who has a large Domino Intranet, as well as a new Portal site that is externally accessible by employees, and they are looking to start integrating the two, with the eventual goal of migrating totally to Portal. In the meantime the Por
tal should have a link to the intranet. However an employee can not access the Intranet externally so ideally the link should be hidden when they are not accessing the Portal internally.
I read in "WebSphere Portal Best Practices" (
http://publib-b.boulder.ibm.com/Red...p4100.html?Open )
that they recommend having two separate User Ids for internal and external access, which is what IBM employee's have. Presumably they also have seperate Portal sites which is fine, but quite expensive for smaller companies, especially when they are first
getting started with Portal. If you don't have two seperate Portal sites then how do you stop employee's logging in from outside the network with their internal User Ids?
Any thoughts appreciated...
| |
| SpiritWolfX 2006-07-21, 8:08 pm |
| Using the http session information you can get the IP address for the individual accessing the page. Compare this IP address to the range of IP addresses assigned to the company internally and you can eliminate anyone that is not within the range.
For us the starting IP address internally is 10. Anything that is accessing from outside the network will start with a different number, such as 104.116... .
quote:
Originally posted by
Is there a best practise for determining whether a user is accessing a portal from within or outside of the network?
I work for a client who has a large Domino Intranet, as well as a new Portal site that is externally accessible by employees, and they are looking to start integrating the two, with the eventual goal of migrating totally to Portal. In the meantime the Por
tal should have a link to the intranet. However an employee can not access the Intranet externally so ideally the link should be hidden when they are not accessing the Portal internally.
I read in "WebSphere Portal Best Practices" (
http://publib-b.boulder.ibm.com/Red...p4100.html?Open )
that they recommend having two separate User Ids for internal and external access, which is what IBM employee's have. Presumably they also have seperate Portal sites which is fine, but quite expensive for smaller companies, especially when they are first
getting started with Portal. If you don't have two seperate Portal sites then how do you stop employee's logging in from outside the network with their internal User Ids?
Any thoughts appreciated...
|
|
|
|
|