FAQ
Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform

English

Türkçe

English

Türkçe

Appearance

Basic

What is the Portal; how do users reach several applications with a single sign-in? ​

Short answer

Portal is the common entry point where users log in once and reach the published applications with the same session; it is set up by setting the Gateway Mode value of an AGS-enabled vService to Portal. The user is verified in the Flowchart flow of the portal and moves to the applications in the Portal Applications list without entering the password again; the Access Mode selected for each application determines how the session is carried to the application. If AGS is on in the vService of the application as well, this vService is put into Portal Application mode and the portal is selected in the Trusted Portals list.

How Does It Work? ​

  1. The user comes to the address of the portal (Portal URL); if the user has no session, the user enters the login flow of the portal.
  2. When the flow ends with Allow, the portal session is opened and the user sees the portal page on which the published applications are listed.
  3. When the user moves to an application, the session is carried according to Access Mode: in Domain Tunnel and Private Domain Tunnel, the request is tunneled from the portal vService to the vService of the application; in TR7 Application, the application is accessed from its own vService address and that vService accepts the portal session (What do the Portal Access Mode options (Domain Tunnel, TR7 Application, Private Domain Tunnel) mean?).
  4. If a user who has no session comes directly to the address of an application, the user is redirected to the portal. If the portal cookie does not reach the domain name of the application, after the login the session is carried to the application from the handoff address of the portal with a timed and signed token.

Portal Setup in TR7 ​

SideFieldWhat it determines
Portal vServiceGateway Mode = PortalThe vService working as a portal
Portal vServicePortal URL (mandatory)The address of the portal open to the users; the visitors who have no session are redirected here
Portal vServicePortal ApplicationsFor each application, Application Name, Access Mode, Application URL and Application vService
Portal vServiceCookie DomainThe domain name for which the portal session cookie is valid; if the application domain names are under it, the cookie reaches the application directly
Application vServiceGateway Mode = Portal Application, Trusted PortalsThe portal session being accepted in the application

The fields are in the Gateway Mode section of the General Settings window on the Flowchart tab of the AGS-enabled vService; the published applications are listed in the Portal & Applications section of the AGS Management tab.

Common Misconceptions ​

  • "When the application is added to the Portal Applications list, it accepts the portal session by itself." If AGS is on in the vService of the application, the vService is put into Portal Application mode and the portal is selected in the Trusted Portals list; a vService in Standalone Application mode does not accept the session of the portal.
  • "The Default Backend Services of the portal vService serve the user with a session." In Portal mode, the default target is the AGS engine; the requests that have a session and do not match the Conditional Backend Services rules go to the portal page.
  • "With AGS Activation Condition, a path on the portal vService is left outside AGS." In Portal mode, even the requests that do not match the condition go to the AGS engine if they do not match the Conditional Backend Services rules (What do AGS Activation Condition and AGS Root Path determine?).

How it is done in the documentation

Related questions