The integration methods in the previous chapter largely ignored the physical location of the PortalGuard and target servers.Since PortalGuard relies on the HTTP protocol and RESTful design principles (link), it offers a high degree of flexibility in this area.
When deciding “where” PortalGuard will be installed, it is imperative to first have an understanding of the user access scenarios by answering the following questions:
- Who will be accessing PortalGuard?
- Company employees?
- External customers?
- Where will they be located?
- On the LAN?
- From the internet?
- From a mobile device?
- What PortalGuard services will they be accessing?
- Self-service account management?
- Multiple factor authentication?
- Password management/synchronization?
Once these questions are answered, it helps dictate how PortalGuard should be deployed. The two sections below briefly lay out general guidelines for this topic.
For a fuller discussion on making PortalGuard available in a load balanced manner, please see Chapter 9 in the PortalGuard Administrator’s Guide (link).