This page lists the HTTP cookies used by the jtel portal.
JSESSIONID
Purpose
This cookie represents the active portal session. It allows the application server to associate requests with the correct logged-in user and keep the user authenticated while navigating through the CarrierPortal.
Property | Value |
|---|---|
Type | Session cookie |
Used when | During an active CarrierPortal session |
Path | /CarrierPortal |
Lifetime | Browser/application session |
SameSite | None |
Secure | Yes |
Managed by | Application server |
SERVERID
Purpose
This cookie is used for server affinity in environments with multiple application servers. It helps ensure that requests from the same browser session are routed to the same backend server where required.
Property | Value |
|---|---|
Type | Session cookie |
Used when | Requests are routed through a load balancer |
Path | / |
Lifetime | Session |
Content | Application server identifier, e.g. jboss1 |
JTEL.Portal.Login.Request.Url
Purpose
This cookie stores the URL the user originally attempted to access before authentication was required. After a successful login, the portal can redirect the user back to the intended page.
Property | Value |
|---|---|
Type | Persistent cookie |
Used when | A user is redirected to the login page |
Path | / |
Max-Age | 31,536,000 seconds |
Lifetime | 1 year |
SameSite | None |
Secure | Yes |
JTEL.Portal.Login
Purpose
This cookie supports the remembered-login functionality. When the user chooses to save their login information, the portal stores an identification value that can be used to recognize the user during a later visit and simplify the login process.
The login information is not stored as plain text in the cookie.
Property | Value |
|---|---|
Type | Persistent cookie |
Used when | The user enables storage of login information |
Path | / |
Lifetime | Persistent |
Content | Encoded/hashed login identification data |