{"id":7053,"date":"2024-10-17T14:22:13","date_gmt":"2024-10-17T11:22:13","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=announcement&#038;p=7053"},"modified":"2026-10-19T13:08:33","modified_gmt":"2026-10-19T10:08:33","slug":"new-feature-federated-single-sign-on-is-now-available-for-withsecure-elements","status":"publish","type":"announcement","link":"https:\/\/support.withsecure.com\/en\/announcements\/new-feature-federated-single-sign-on-is-now-available-for-withsecure-elements\/","title":{"rendered":"New Feature: Federated Single Sign-On is now available for WithSecure Elements"},"content":{"rendered":"<p><strong>Update 2024-12-03<\/strong>: Added information about WithSecure Elements Identity Security, and WithSecure Elements Exposure Management, which can protect your users from identity-based attacks.<\/p>\n<h2 data-id=\"what-is-federated-sso\"><strong>What is Federated SSO?<\/strong><\/h2>\n<p>Federated single sign-on (FSSO) is a mechanism that allows users to authenticate and access several applications or services across different domains or organizations without the need to log in separately for each.<\/p>\n<p>Users may already be familiar with this if they access their own organization\u2019s systems using the same account, usually the same account they use to log into their workstations. The same account is often used for their email, or Microsoft Teams, meaning they log in once and that\u2019s it.<\/p>\n<p>FSSO simplifies access across various systems by allowing users to authenticate once and move seamlessly between different applications or services. It enhances security and user experience by eliminating the need for multiple logins.<\/p>\n<h2 data-id=\"how-to-use-federated-sso-to-access-withsecure-elements\"><strong>How to use Federated SSO to access WithSecure Elements<\/strong><\/h2>\n<p>Once an organization decides to implement Federated SSO to access WithSecure Elements, there\u2019s a few basic things to do:<\/p>\n<h4 data-id=\"ensure-that-your-domain-users-have-accounts-in-withsecure-elements\"><strong>Ensure that your domain users have accounts in WithSecure Elements<\/strong><\/h4>\n<p>For every user in your organization that should be able to access WithSecure Elements, an <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fuserguides%2Fproduct.html%23business%2Felements-welcome%2Flatest%2Fen%2Ftask_EEBF4BF4DC654BA6B9DB85D931D4E914-latest-en\" target=\"_blank\" rel=\"nofollow noopener ugc\">account must be created<\/a> within Elements.<\/p>\n<p><strong>NOTES:<\/strong><\/p>\n<ul>\n<li>Federated SSO can only work with plain email addresses such as <a href=\"mailto:firstname.lastname@company.org\" target=\"_blank\" rel=\"nofollow noopener ugc\"><strong>firstname.lastname@company.org<\/strong><\/a>. Addresses of the form <a href=\"mailto:firstname.lastname+elements@company.org\" target=\"_blank\" rel=\"nofollow noopener ugc\"><strong>firstname.lastname+elements@company.org<\/strong><\/a> will not work.<\/li>\n<li>Email aliases do not work with FSSO, so always use the primary email address for the account.<\/li>\n<li>IAM administrators can still create accounts outside of federated domains. Any such existing accounts will continue to function and will require an Elements password upon login. The ability to define policies that restrict organization access to federated accounts only will be added in future releases of Elements.<\/li>\n<li>If a linked user cannot be authenticated, for example if they have been removed from the Entra ID domain, they will be unable to access WithSecure Elements.<\/li>\n<\/ul>\n<h4 data-id=\"link-your-domain-to-withsecure-elements\"><strong>Link your domain to WithSecure Elements<\/strong><\/h4>\n<p>As a Global Administrator user within your organization\u2019s Entra ID tenant, you <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fuserguides%2Fproduct.html%23business%2Felements-welcome%2Flatest%2Fen%2Fsetting_up_federated_single_sign_on-latest-en\" target=\"_blank\" rel=\"nofollow noopener ugc\">must link your domain<\/a> to WithSecure Elements.<\/p>\n<p>After successfully linking WithSecure Elements and the Entra ID tenant, the administrator must finally enable FSSO within Elements.<\/p>\n<h4 data-id=\"logging-into-withsecure-elements\"><strong>Logging into WithSecure Elements<\/strong><\/h4>\n<p>Once all the above steps have been completed, users will be able to log into WithSecure Elements with their Entra ID account.<\/p>\n<p><strong>NOTE:<\/strong> The first time the user logs in after federation has been taken into use, they will be prompted for their Elements password <strong>and<\/strong> Entra ID domain password. On future access to WithSecure Elements, the user should be prompted only if there is no valid Entra ID authentication available. <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fuserguides%2Fproduct.html%23business%2Felements-welcome%2Flatest%2Fen%2Flinking_user_identities-latest-en\" target=\"_blank\" rel=\"nofollow noopener ugc\">See the User Guide for more information<\/a>.<\/p>\n<h2 data-id=\"protecting-your-entra-id-users-from-identity-based-attacks\"><strong>Protecting your Entra ID users from Identity-based attacks<\/strong><\/h2>\n<p>Did you know that you can help protect your Entra ID users by taking <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fsolutions%2Fsoftware-and-services%2Fwithsecure-elements-identity-security\" rel=\"nofollow noopener ugc\" target=\"_blank\">WithSecure Elements Identity Security<\/a> into use. <\/p>\n<p>This will protects organizations against identity-based attacks by detecting potentially compromised Microsoft Entra ID identities that are used by attackers to access Microsoft 365 or other cloud-based services.<\/p>\n<h2 data-id=\"minimize-identity-related-risks-using-withsecure-elements-exposure-management\"><strong>Minimize Identity-related risks using WithSecure Elements Exposure Management<\/strong><\/h2>\n<p><a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fsolutions%2Fsoftware-and-services%2Fwithsecure-elements-exposure-management\" rel=\"nofollow noopener ugc\" target=\"_blank\">WithSecure Elements Exposure Management<\/a> is a world class solution for checking your infrastructure for misconfigurations and vulnerabilities. It can be help you minimize risks related to identities by catching for example disabled MFAs, Old passwords, and possible Identity leaks.<\/p>\n<p>\u00a0<\/p>\n<h2 data-id=\"final-note\"><strong>Final Note<\/strong><\/h2>\n<p>You can find comprehensive documentation on the whole process of configuring and using FSSO in the <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fuserguides%2Fproduct.html%23business%2Felements-welcome%2Flatest%2Fen%2Ffederated_single_sign_on-latest-en\" target=\"_blank\" rel=\"nofollow noopener ugc\">Elements User Guide<\/a>.  <strong>Please note:<\/strong> At the time of publishing this article, the localized userguides are still being worked on, so please check the English guide.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Update 2024-12-03: Added information about WithSecure Elements Identity Security, and WithSecure Elements Exposure Management, which can protect your users from identity-based attacks. What is Federated SSO? Federated single sign-on (FSSO)&hellip;<\/p>\n","protected":false},"template":"","announcement_category":[142],"class_list":["post-7053","announcement","type-announcement","status-publish","hentry"],"acf":{"source_system":"vanilla-import","import_hash":"1b9571ddaf07496496240b68a1b119cd4d15bc80","vanilla_article_id":31414,"legacy_author":"AndyF_WS","vanilla_url":"https:\/\/community.withsecure.com\/announcements-en\/kb\/articles\/31414-new-feature-federated-single-sign-on-is-now-available-for-withsecure-elements","vanilla_category_id":142,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7053","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/announcement"}],"version-history":[{"count":1,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7053\/revisions"}],"predecessor-version":[{"id":8458,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7053\/revisions\/8458"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=7053"}],"wp:term":[{"taxonomy":"announcement_category","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement_category?post=7053"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}