Source
Confidentiality of translated content — found from sitemap — Transifex
Checked for Transifex on 1 Nov 2026
- Page
- https://help.transifex.com/en/articles/6641251-saml-single-sign-on-sso
- Checked
- 1 Nov 2026, 10:08 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:d8d3b7b01175d903d00f9bcc7da3b207e47fa230ae3e6977ad6800fd37820c5e
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SAML plan requirement Report an error
“📝Note: This feature is available only on our Enterprise Plus plan.”
-
SAML version Report an error
“Transifex supports SAML 2.0.”
-
SAML supported idp Report an error
“Okta is the only officially supported Identity Provider (IdP) at the moment, but any SAML2 Identity Provider should work.”
-
SAML one idp per org Report an error
“Only one Identity Provider can be configured per organization.”
-
SAML acs URL Report an error
“SSO URL -> https://app.transifex.com/saml/acs/ Entity ID -> https://app.transifex.com/saml/acs/”
-
SAML sign on URL Report an error
“Sign on URL: https://app.transifex.com/saml/<your_organization_slug>/sso/”
-
SAML config requirements Report an error
“In order to configure the SSO in Transifex, you must provide our support team with the following: OKTA login URL (It should look something like this: https://example.okta.com/app/********/exk7hbhohiaRPuFSW417/sso/saml) X.509 Certificate, issued by OKTA. Issuer: A unique ID assigned by OKTA that identifies the account that uses SSO.”
-
SAML custom session timeout Report an error
“Each SSO-enabled organization can define a custom session timeout setting for its organization in the SSO settings.”
-
Default session timeout Report an error
“If the user logs in from the login form (hybrid login), the default session timeout (the default session expiration is one month) is used.”
-
SSO 2FA exclusive Report an error
“When SSO and 2FA are both enabled for a Transifex user, only one method can be utilized during the login process.”
-
SSO enforcement optional Report an error
“Enabling SAML for an organization will NOT mandate all users to sign in only via SAML: the user can select their type of login from the main login page.”
-
SSO enforce option Report an error
“To mandate all users to sign in only via SAML, enable the enforce SSO option:”
-
SSO failed login notifications Report an error
“To stop getting email notifications about unsuccessful login attempts by your users to your organization, you can use the following steps:”
-
SAML session migration Report an error
“If a one-time migration of the active user sessions is desired upon activation of the Single Sign-On login. A date threshold, after which the one-time migration will not be executed, even if it is enabled and there are still active user sessions.”
-
SAML email match requirement Report an error
“The user's email address must be present and the same in both Transifex and Okta.”
-
Okta 2FA support Report an error
“Okta supports 2FA. Please contact your IT department to enable it for your organization.”
-
SSO access logging Report an error
“The access type is logged in Transifex (in case the old Transifex username coincides with the SSO username, for example).”
Scores citing this record
- The App Developer Confidentiality of translated content
- The Data Protection Officer Confidentiality of translated content
- The Data Protection Officer Pricing transparency
- The In-House Document Translator Confidentiality of translated content
- The In-House Document Translator Pricing transparency
- The E-Commerce Marketer Confidentiality of translated content
- The E-Commerce Marketer Pricing transparency
- The Localization Manager Confidentiality of translated content
- The Localization Manager Pricing transparency
- The Skeptic Confidentiality of translated content
- The Skeptic Pricing transparency