{"component": "clause", "props": {"groups": [{"size": 2, "snippet_links": [{"key": "responsible-for", "type": "clause", "offset": [15, 30]}, {"key": "industry-standard", "type": "clause", "offset": [81, 98]}, {"key": "cooperation-with", "type": "clause", "offset": [119, 135]}, {"key": "agrees-to", "type": "clause", "offset": [154, 163]}, {"key": "provided-that", "type": "clause", "offset": [192, 205]}, {"key": "form-no", "type": "clause", "offset": [252, 259]}, {"key": "effective-date-of-this-agreement", "type": "definition", "offset": [301, 333]}], "samples": [{"hash": "lhYSBU5VK35", "uri": "/contracts/lhYSBU5VK35#single-sign", "label": "Master Data Processing Services Agreement (Independent Bank Corp)", "score": 23.5434633812, "published": true}, {"hash": "6cmCbj3tZMJ", "uri": "/contracts/6cmCbj3tZMJ#single-sign", "label": "Master Data Processing Services Agreement (Independent Bank Corp)", "score": 23.3846680356, "published": true}], "snippet": "On Customer is responsible for providing specifications from target vendor in an industry standard format and securing cooperation with target vendor. Q2 agrees to honor the following pricing provided that Customer purchases via a separate sales order form no later than forty-five (45) days from the Effective Date of this Agreement:", "hash": "a5a0cfa87cd92d6a825d1392270b0a27", "id": 1}, {"size": 1, "snippet_links": [], "samples": [{"hash": "h5TQT94bhyL", "uri": "/contracts/h5TQT94bhyL#single-sign", "label": "Software Subscription and Support Services Agreement", "score": 32.7186706106, "published": true}], "snippet": "ON (SSO) REQUIREMENTS Clever Google SFUSD \u2013 ADFS (Local) None Other", "hash": "4e113d333d95c6dd100b65d468c30374", "id": 5}, {"size": 1, "snippet_links": [{"key": "access-to", "type": "definition", "offset": [20, 29]}, {"key": "bill-pay", "type": "definition", "offset": [30, 38]}], "samples": [{"hash": "tDoXvyZauq", "uri": "/contracts/tDoXvyZauq#single-sign", "label": "Internet Banking Agreement", "score": 26.3552361396, "published": true}], "snippet": "On Allows automatic access to Bill Pay and Order Checks without having to re-enter an Access ID and Password.", "hash": "1882590f22d13accc2cc29e2c067e70a", "id": 2}, {"size": 1, "snippet_links": [], "samples": [{"hash": "2TOus8iN8lc", "uri": "/contracts/2TOus8iN8lc#single-sign", "label": "Cloud Services Agreement", "score": 32.6795438913, "published": true}], "snippet": "On AddOn", "hash": "8aae901f2e5007a21992340f04140f4a", "id": 3}, {"size": 1, "snippet_links": [{"key": "user-authentication", "type": "clause", "offset": [43, 62]}, {"key": "access-to", "type": "definition", "offset": [67, 76]}], "samples": [{"hash": "7fuC3yU4KXv", "uri": "/contracts/7fuC3yU4KXv#single-sign", "label": "Service Agreement", "score": 34.164728161, "published": true}], "snippet": "On (SSO) integration options to streamline user authentication and access to 1Password", "hash": "f346568e943534e066bd9418de49f942", "id": 4}, {"size": 1, "snippet_links": [{"key": "custom-applications", "type": "clause", "offset": [7, 26]}, {"key": "authentication-credentials", "type": "clause", "offset": [65, 91]}, {"key": "authentication-and-authorization", "type": "clause", "offset": [172, 204]}, {"key": "multiple-applications", "type": "clause", "offset": [212, 233]}, {"key": "client-configurations", "type": "clause", "offset": [246, 267]}, {"key": "not-supported", "type": "clause", "offset": [316, 329]}, {"key": "for-ibm", "type": "definition", "offset": [763, 770]}], "samples": [{"hash": "cMAWpoFmQu1", "uri": "/contracts/cMAWpoFmQu1#single-sign", "label": "Services Contract", "score": 33.3711797958, "published": true}], "snippet": "On for Custom Applications Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign\u2010On service. Single Sign\u2010On for PeopleSoft Enterprise Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign\u2010On service. Single Sign\u2010On for IBM Tivoli AccessManager Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign\u2010On service.", "hash": "e2ac4a66a2dc20f5a8f8432a9e389eed", "id": 6}, {"size": 1, "snippet_links": [{"key": "user-groups", "type": "definition", "offset": [107, 118]}, {"key": "enterprise-customer", "type": "definition", "offset": [173, 192]}, {"key": "active-directory", "type": "clause", "offset": [198, 214]}, {"key": "with-third-parties", "type": "clause", "offset": [288, 306]}], "samples": [{"hash": "5VSBAlVRY5B", "uri": "/contracts/5VSBAlVRY5B#single-sign", "label": "Contract Agreement", "score": 19.5427789185, "published": true}], "snippet": "On (SSO) Integration Single Sign-On (SSO) will take place during implementation. All usernames, passwords, user groups, roles, and account names will be managed locally by \u201cEnterprise Customer\u201d via Active Directory. All updates will be synchronized with Schoology. SSO can be established with third parties, via Schoology\u2019s custom SSO script.", "hash": "bf7a5cfe2de3b9ddc2398b88b1f6b876", "id": 7}, {"size": 1, "snippet_links": [{"key": "for-\u2587", "type": "clause", "offset": [3, 8]}, {"key": "authentication-credentials", "type": "clause", "offset": [50, 76]}, {"key": "authentication-and-authorization", "type": "clause", "offset": [157, 189]}, {"key": "multiple-applications", "type": "clause", "offset": [197, 218]}, {"key": "client-license", "type": "clause", "offset": [226, 240]}, {"key": "client-configurations", "type": "clause", "offset": [551, 572]}, {"key": "not-supported", "type": "clause", "offset": [621, 634]}], "samples": [{"hash": "cMAWpoFmQu1", "uri": "/contracts/cMAWpoFmQu1#single-sign", "label": "Services Contract", "score": 33.3711797958, "published": true}], "snippet": "On for \u2587\u2587\u2587\u2587 Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. Valid Client license Appropriate Single Sign\u2010On service. Single Sign\u2010On for Central AuthenticationService (CAS) Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign\u2010On service.", "hash": "ef974bf1aeb9cb9c3837e305f392df4e", "id": 8}, {"size": 1, "snippet_links": [{"key": "authentication-credentials", "type": "clause", "offset": [64, 90]}, {"key": "authentication-and-authorization", "type": "clause", "offset": [171, 203]}, {"key": "multiple-applications", "type": "clause", "offset": [211, 232]}, {"key": "client-configurations", "type": "clause", "offset": [245, 266]}, {"key": "not-supported", "type": "clause", "offset": [315, 328]}], "samples": [{"hash": "cMAWpoFmQu1", "uri": "/contracts/cMAWpoFmQu1#single-sign", "label": "Services Contract", "score": 33.3711797958, "published": true}], "snippet": "On for RSA Access Manager Allows OnBase to be configured to use authentication credentials from selected single sign\u2010on service vendors. Single sign\u2010on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign\u2010On service.", "hash": "8f447777e69b02786879fdbb54df89bd", "id": 9}, {"size": 1, "snippet_links": [{"key": "open-calls", "type": "clause", "offset": [32, 42]}, {"key": "the-open", "type": "clause", "offset": [138, 146]}, {"key": "sign-up", "type": "definition", "offset": [235, 242]}, {"key": "following-the", "type": "definition", "offset": [428, 441]}, {"key": "the-protocol", "type": "clause", "offset": [515, 527]}, {"key": "the-client", "type": "definition", "offset": [560, 570]}], "samples": [{"hash": "jFvHnKLYBaB", "uri": "/contracts/jFvHnKLYBaB#single-sign", "label": "Grant Agreement", "score": 23.6187542779, "published": true}], "snippet": "On between core Marketplace and Open Calls platforms\u200c The integration between the two individual platforms, the core L4MS Marketplace and the open calls platform, a Single Sign-On functionality has been developed, that allows users to sign up and login to the L4MS Marketplace, and then use the open calls platform with the same credentials, without having to sign up or log in again. The Single Sign-On feature was implemented following the OAuth2 protocol, where the core Marketplace serves as the server side of the protocol, and the open calls platform as the client side.", "hash": "d82d3d4bdc8867b64a89b10ef125b649", "id": 10}], "next_curs": "ClQSTmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjALEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhRzaW5nbGUtc2lnbiMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"children": [["", ""], ["objections", "Objections"], ["data-transfer", "Data Transfer"], ["type-2-objections", "Type 2 Objections"], ["accuracy-of-the-data", "Accuracy of the Data"]], "size": 14, "title": "Single Sign", "parents": [["service-description", "Service Description"], ["standard-service", "Standard Service"], ["cloud-service", "Cloud Service"], ["optional-services", "Optional Services"], ["the-glueing-service", "The Glueing Service"]], "id": "single-sign", "related": [["execution-in-counterparts-facsimile-signatures", "Execution in Counterparts; Facsimile Signatures", "Execution in Counterparts; Facsimile Signatures"], ["facsimile-signatures", "Facsimile Signatures", "Facsimile Signatures"], ["facsimile-signature", "Facsimile Signature", "Facsimile Signature"], ["counterparts-and-facsimile-signatures", "Counterparts and Facsimile Signatures", "Counterparts and Facsimile Signatures"], ["counterparts-and-facsimile-signature", "Counterparts and Facsimile Signature", "Counterparts and Facsimile Signature"]], "related_snippets": [], "updated": "2025-07-07T12:37:53+00:00", "also_ask": ["What are the strategic advantages and drawbacks of a Single Sign clause in multi-party agreements?", "Which essential elements must be included to ensure the Single Sign clause is enforceable and unambiguous?", "What are the primary legal risks or loopholes that could undermine the effectiveness of a Single Sign clause?", "How does the Single Sign approach compare to traditional multi-signature or counterpart execution clauses?", "What standards do courts apply when determining the validity and enforceability of a Single Sign clause in disputes?"], "drafting_tip": "Define 'Single Sign' precisely to avoid ambiguity; specify the parties authorized to sign to ensure enforceability; clarify the effect of a single signature to prevent disputes.", "explanation": "The Single Sign clause establishes that a party is required to execute a document or agreement only once, rather than signing multiple copies or versions. In practice, this means that a single, original signature is sufficient to bind the parties, and additional signatures on duplicate documents are not necessary. This clause streamlines the execution process, reduces administrative burden, and helps prevent confusion or disputes over which version of a document is the official, binding one."}, "json": true, "cursor": ""}}