Glossary
Glossary
| Term | Definition |
|---|---|
| Backup area | Area that receives files after download; they stay there according to the retention policies. |
| Basic | HTTP authentication scheme in which the user name and password are sent Base64-encoded in the Authorization header. In Riversoft STCP DirectLink, it is accepted only at sign-in. |
| Bearer | Authentication scheme in which an access token is sent in the Authorization header or in the session cookie. Required on protected API routes. |
| Cloudflare Turnstile | Cloudflare anti-automation challenge, optional on sign-in, first access and password recovery. |
| Download area | Area with the files available for the user to receive. |
| Impersonation token | Long-lived token generated in the supervision interface for technical integrations, with a registered session identifier. |
| JWKS | JSON Web Key Set: JSON format for publishing the public keys used to validate JWTs. |
| JWT | JSON Web Token: signed token that carries trusted information (claims). |
| MFA | Multi-factor authentication: second factor (PIN by email or SMS, or TOTP code) required after the password. |
| MFT | Managed File Transfer: file transfer with control, security and traceability. |
| OAuth 2.0 | Authorization standard used to issue the Bearer token and for SSO. |
| OAuth 2.1 | Revision of OAuth 2.0 that makes security practices such as PKCE mandatory and does not include the password grant. |
| OpenID Connect | Identity layer on top of OAuth 2.0, used for SSO with external providers. |
| Operator | Person who accesses the Riversoft Console Portal or the Riversoft STCP Gemini API to configure and track transfers, such as stcpadmin. Not to be confused with the transfer user. |
| PIN | Numeric code sent by email or SMS to confirm an operation: secure link download, MFA or password change. |
| SAML 2.0 | Identity federation standard used for SSO with corporate providers. |
| Secure link | Signed, time-limited link tied to a file and its recipient (or to an MFA or password operation). |
| Security code | Code (PIN) sent to the email address or mobile number linked to a file, required to download through a secure link; it has a limited lifetime. |
| Session cookie | __Host-dirl_session cookie that keeps the user signed in to the portal; issued with HttpOnly, Secure and SameSite=Strict. |
| SSO | Single Sign-On: access with an identity provider account (Google, Microsoft, Apple, SAML providers, etc.). |
| Token exchange | Exchange of a JWT issued by a trusted provider for a Riversoft STCP DirectLink Bearer token (RFC 8693). |
| Transparent upload | Upload in which the request body is the file itself, with any Content-Type, without an envelope. |