Glance DOCS

Service Target URLs (STUs)

How to construct and use Service Target URLs (STUs) to provide direct, one-click access to Glance sessions and account management tools, for both standard and Single Sign-On (SSO) environments.

What is a Service Target URL?

A Service Target URL (STU) is a hyperlink that links directly to a specific Glance service or task.

For example, when a Glance user visits an Agent Join STU, they immediately see the page where they can enter a session code provided by a customer to join a session. (If the user is not yet logged in to Glance, they are prompted to log in first).

Agent Join Screen

The base URL for the Agent Join page is:

TEXT
https://www.glance.net/agentjoin/agentjoin.aspx

When setting up Glance for your users, you can embed STUs in their web portal or application. For example, to produce a "Join Session" link, add this HTML code:

HTML
<a href="[https://www.glance.net/agentjoin/agentjoin.aspx](https://www.glance.net/agentjoin/agentjoin.aspx)">Join a Glance Session</a>

STUs without Single Sign-On

These URLs are for standard accounts that do not use SAML SSO.

  • https://www.glance.net/agentjoin/AgentJoin.aspx – Prompts the agent for a session key.
  • https://www.glance.net/agentjoin/AgentView.aspx?SessionKey=1234 – Joins a specific session directly. Replace 1234 with the actual session key.

Identity Parameters

You can add these parameters to either the AgentJoin or AgentView STUs to identify the agent. When available, Glance displays this identity to the visitor as the session starts.

  • name=User+Name – displays the user's personal information, including name, email, and phone number, as a courtesy to individuals using Glance to request assistance.
  • email=user@example.com – Displays the user's email.
  • phone=(111)222-3333 – Displays the user's telephone number.

Control Parameters (AgentJoin Only)

The AgentJoin URL supports optional parameters to modify its behavior.

  • viewersamewindow=1 – Initiates the session viewer within the same browser window that displays the session key prompt. If omitted, Glance launches the viewer in a new window by default.

The following optional parameters control the prompt on the AgentJoin page. For more information on configuring these, please contact Glance Customer Success.

  • mode=universaljoin
  • mode=chatinvitation
  • mode=smsinvitation

STUs with Single Sign-On

For accounts utilizing SAML 2.0 Single Sign-On, you must use SSO-specific STUs. These require an identity provider identifier, which corresponds to the account's numeric Group ID.

Note
In the examples below, we use a Group ID of EXAMPLE. You must replace this with your specific Glance Group ID or Partner ID.

Accessing any SSO STU starts a service-provider-initiated login if the user is not yet signed on.

These STUs give direct access to sessions. When a Glance user visits one of these STUs, they immediately see the session page.

  • https://www.glance.net/agentjoin/AgentJoin.aspx?idpid=EXAMPLE – Prompts for a session key.
  • https://www.glance.net/agentjoin/AgentView.aspx?idpid=EXAMPLE&SessionKey=1234 – Joins the session directly. Replace 1234 with the actual session key.

You may use the optional identity parameters mentioned above with these STUs.

To start an interactive session on the Glance Account Management page:

TEXT
https://www.glance.net/account/GetLoginKey.aspx?sso=1&idpid=EXAMPLE&redirect=/account/AccountSummary.aspx

To obtain a Login Key for use by native client software:

TEXT
https://www.glance.net/account/GetLoginKey.aspx?sso=1&idpid=EXAMPLE

To show a SAML troubleshooting page:

TEXT
https://www.glance.net/account/GetLoginKey.aspx?sso=1&test=11&idpid=EXAMPLE

For more information on troubleshooting, see the SAML Troubleshooting Guide.

Alternative identifiers for SSO

If you do not wish to use idpid=EXAMPLE (Group ID), you can use one of the following alternatives:

  1. Group Name (idpname) Use idpname=EXAMPLE. Glance will use the unique group name rather than the number. Replace EXAMPLE with your account's group name provided by Glance Support.

  2. Partner Token (idptoken) Use idptoken=TOKENVALUE. Glance uses the value from the Unique Account Identifier field on the SAML provisioning screen. Replace TOKENVALUE with the name you put in that field. This is suitable for Salesforce Organization IDs or Azure tenant names.

  3. Username (idpusername) Use idpusername=USER.glance.net. Glance uses the specific username to look up the account group. This is convenient if the group name is unknown. Replace USER.glance.net with the Glance Address of any user on the account.