SP Entity ID*<\/strong><\/h3>\n\n\n\nThis is the unique, case-sensitive<\/strong> identifier used by the SP. The SP will likely supply you with this value. <\/p>\n\n\n\nIt may also be referred to as:<\/p>\n\n\n\n
\nAudience<\/li>\n\n\n\n Entity ID<\/li>\n\n\n\n Identifier<\/li>\n\n\n\n Service Provider Issuer<\/li>\n\n\n\n Audience Restriction<\/li>\n<\/ul>\n\n\n\n <\/p><\/div>
Tip:<\/strong> \nIn the SP metadata file, the SP Entity ID is the entityID<\/strong> attribute value of the EntityDescriptor<\/strong> element.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\nACS URLs *<\/strong><\/h3>\n\n\n\nThis is the endpoint to which JumpCloud will send SAML Responses (containing Assertions). JumpCloud supports multiple ACS URLs. The SP will supply you with this value and may refer to it as:<\/p>\n\n\n\n
\nDestination<\/li>\n\n\n\n Recipient<\/li>\n\n\n\n SAML Assertion Endpoint URL<\/li>\n\n\n\n ACS URL, Assertion Consumer Service URL<\/li>\n\n\n\n Consume URL<\/li>\n<\/ul>\n\n\n\n <\/p><\/div>
Tip:<\/strong> \nIn the SP metadata file, the ACS URL is the location<\/strong> attribute value of the AssertionConsumerService<\/strong> element. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\nSP Certificate*<\/strong><\/h3>\n\n\n\nThis is the public certificate used by SPs for SAML Requests. If you can download the SP\u2019s public certificate, please do so and upload it here. If you have the SP\u2019s metadata file, it may contain the certificate in the X509 Certificate<\/strong> element. If so, you may copy and paste the certificate contents into a file and upload it to your JumpCloud configuration. Ensure that the SP\u2019s certificate is Base64 encoded before you upload it.<\/p>\n\n\n\nSAMLSubject NameID*<\/strong><\/h3>\n\n\n\nThis is the user identifier that will be sent as the SAMLSubject’s NameID. By default, the SAMLSubject\u2019s NameID is the user’s email. You can change it to username<\/strong>, firstname<\/strong>, lastname<\/strong>, or description<\/strong>, but only change this value if the SP requires a NameID other than email. Use description<\/strong> if you need to use an alternate value for emailaddress<\/strong>, username<\/strong>, firstname<\/strong>, or lastname<\/strong>. <\/p>\n\n\n\nSAMLSubject NameID Format*<\/strong><\/h3>\n\n\n\nThis is the format that will be sent for the SAMLSubject’s NameID. Only change this value if the SP requires a specific NameID format.<\/p>\n\n\n\n
Signature Algorithm*<\/strong><\/h3>\n\n\n\nJumpCloud SSO SAML connectors support SHA-256 certificates by default. Although JumpCloud supports SHA-1 certificates, we recommend using SHA-256 for stronger security. <\/p>\n\n\n\n
Sign<\/strong>*<\/h3>\n\n\n\nSigning a SAML authentication response or SAML authentication assertion ensures message integrity when delivered to the SP. There are three choices:<\/p>\n\n\n\n
\nResponse <\/strong>– this is the default setting. All SAML authentication responses from JumpCloud to the SP will be signed. The response can be validated by the SP using JumpCloud’s signing certificate (X.509 Certificate) that has been uploaded to the SSO connector.<\/li>\n\n\n\nAssertion <\/strong>– the attribute statement within the response is signed. This adds another layer of security where JumpCloud will encrypt the assertion using the SP’s public certificate and sends it to the SP who will decrypt it using the private key. <\/li>\n\n\n\nAssertion and Response<\/strong> – both assertions and responses are signed.<\/li>\n<\/ol>\n\n\n\nDefault RelayState <\/strong><\/h3>\n\n\n\nEnter a value that designates the default location to which your users will be redirected after single sign-on is complete. It will be sent by JumpCloud as the RelayState either in IdP-initiated SSO or if no RelayState is received from the SP during SP-initiated flow. <\/p>\n\n\n\n
The SP may supply you with this value and refer to it as:<\/p>\n\n\n\n
\nTarget URL<\/li>\n\n\n\n RelayState<\/li>\n\n\n\n Target<\/li>\n<\/ul>\n\n\n\nLogin URL<\/strong><\/h3>\n\n\n\nIf this application only supports SP initiated authentication, insert the URL users need to log in to this application.<\/p>\n\n\n\n
IDP URL*<\/strong><\/h3>\n\n\n\nThe IDP URL is the location to which the SP will send SAML requests and at which a user will authenticate. Please change this value to a plaintext string unique to the SP. The value you input will serve as the end of the IDP URL. <\/p>\n\n\n\n
The SP will require the IDP URL and may refer to it as:<\/p>\n\n\n\n
\nIdentity Provider Target URL<\/li>\n\n\n\n SSO Login URL<\/li>\n\n\n\n Redirect URL<\/li>\n\n\n\n Identity Provider Endpoint<\/li>\n<\/ul>\n\n\n\n <\/p><\/div>
Note:<\/strong> \nTake note of the entire URL (including the portion you edited) for later use.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
<\/p><\/div>
Tip:<\/strong> \nSometimes the SP has an optional field for an IDP Logout URL. Use https:\/\/console.jumpcloud.com\/userconsole\/<\/kbd> to send users back to the user console after they logout.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\nDeclare Redirect Endpoint<\/strong><\/h3>\n\n\n\nSelect this option only if the SP requires that your IDP metadata file contains a redirect endpoint.<\/p>\n\n\n\n
Attributes<\/strong><\/h3>\n\n\n\nUser Attributes<\/strong><\/h4>\n\n\n\nConfigure user attributes to be sent to the SP in assertions. User attributes are unique to each user. You can include attributes for standard user detail attributes or for custom attributes. For example, you can include standard attributes for users\u2019 employee ID and department, or you can include a custom attribute for users\u2019 application ID. Standard attributes are configured in the User Panel Details tab’s User Information<\/strong> and Employee Information<\/strong> sections.<\/strong><\/p>\n\n\n\nConstant Attributes<\/strong><\/h4>\n\n\n\nConfigure any constant-value attributes to be sent to the SP in assertions. The same values will be sent for all users. For example, a constant attribute for session duration limits session times for all users of the application, or SP.<\/p>\n\n\n\n
\nClick add attribute<\/strong> to add a constant attribute. To remove an attribute, click the trash<\/strong> icon.<\/li>\n<\/ul>\n\n\n\nInclude Group Attribute <\/strong><\/h4>\n\n\n\nSelect to include the groups a user is a member of in SAML assertions. When this option is selected, all groups that connect the user to the application are included in assertions to that application. The Groups Attribute Name<\/strong> is the SP’s name of the group attribute. By default, the attribute name is memberOf<\/kbd>.<\/p>\n\n\n\n\nWhen this option is selected, you must include a Groups Attribute Name<\/strong>. You will receive an error when you attempt to activate (create) or save (edit) the connector if you select this option and leave Groups Attribute Name<\/strong> blank.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"Use JumpCloud SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications […]<\/p>\n","protected":false},"author":205,"featured_media":0,"template":"","meta":{"_acf_changed":false,"_oasis_is_in_workflow":0,"_oasis_original":0,"_oasis_task_priority":"2normal","inline_featured_image":false,"footnotes":""},"support_category":[2855,2902],"support_tag":[],"coauthors":[2839],"acf":[],"yoast_head":"\n
SSO Application Connector Fields - JumpCloud<\/title>\n \n \n \n \n \n \n \n \n \n \n \n\t \n\t \n\t \n \n \n\t \n\t \n\t \n