Single Sign-on (SAML 2.0)



The Security Assertion Markup Language (SAML) is an XML-based standard to exchange authentication and authorization information. SAML was developed by the security services technical committee of the Organization of the Advancement of Structured Information Standards (OASIS). SAML allows federated systems with different management systems to interact through simplified and single sign-on exchanges. A technical overview is available from OASIS.

OASIS cites the following advantages of SAML:

  • SAML abstracts the security framework away from platform architectures and particular vendor implementations. Making security more independent of the application logic is an important tenet of Services-Oriented Architecture.
  • SAML does not require user information to be maintained and synchronized between directories.
  • SAML enables single sign-on by allowing the user to authenticate at an identity provider and access service providers without additional authentication. In addition, identity federation (linking multiple identities) with SAML allows for a better-customized user experience at each service while promoting privacy.
  • Using SAML to “reuse” a single act of authentication (such as logging in with a username and password) multiple times across multiple services can reduce the cost of maintaining account information. This burden is transferred to the identity provider.
  • SAML can act to push responsibility for proper management of identities to the identity provider, which is more often compatible with its business model than that of a service provider.

Here, you will find some helpful information on configuring a single sign-on using SAML for your Yodeck account.

Advanced Settings

Group Managed Service accounts are perfect identity solutions for services running on multiple hosts, and using group password management requires no administration overhead as password management is handled automatically using known Servers across multiple hosts.

If you intend to configure a federation server farm environment in Active Directory Federation Services (ADFS), you must create and configure a dedicated service account in Active Directory Domain Services (ADDS) where the farm will reside. You then configure each federation server in the farm to use this account. You must complete the following tasks in your Yodeck Account when you want to allow client computers on the corporate network to authenticate to any of the federation servers in an ADFS farm using Windows Integrated Authentication.

  1. Attribute name for NameID: Choose if you want to use the default NameID or to set another Attribute of your choice.
  2. User’s Name: Keep the same User Name (Yodeck’s Username- email) or overwrite it and set it to your ADFS’s user details.
  3. Automatically Create Users: Enable this to use ‘Just-in-Time Provisioning’ with SAML, i.e., to automatically create new authorized Users coming in from your Identity Provider.
  4. Use SAML Group Access: Enable this to modify User permissions based on a SAML Group automatically. Use Groups to Permissions Mappings to specify the Permissions that each Group has.
    1. Type a name for your Group.
    2. By clicking the grey button called “Add Group Mapping, “you can create groups like your ADFS groups. The users joining this group will inherit the Group’s Account Permissions and Roles. Each Group can have different Account Permissions.
    3. If you have the Workspace feature, you can also set different roles for this group by clicking the “Add Role” button.

Groups to Permissions Mapping setup wizard

Enable this to modify User permissions based on a SAML Group automatically. 

Each user Group can be mapped with a SAML Group like an ADFS group. The users joining this group will inherit the Group’s Account Permissions and Roles. Each user Group can have different Account Permissions.

  1. Type a name for your Group
  2. By default, the already existing user Groups will be displayed by enabling the SAML Group Access.
  3. By Clicking the edit button on the right side of each Group record, you can add the SAML Group name you want to map with. 

How to configure SAML Group Access with Azure

By enabling the option “Use SAML Group Access,” you can automatically modify the user’s permissions based on the SAML Group.  

Before this option is activated, the following steps must be completed.

How to configure SSO with Azure Active Directory (Microsoft Entra)

Automatically Create Users must be enabled.

Configure SAML Group Access in the Yodeck Portal

  1. Login to your Yodeck account as an administrator.
  2. Navigate to Account Settings > SSO > Advanced Settings from the top right menu.
  3. Enable the Use SAML Group Access option.

The first column of the list, “Group Name” contains the names of the groups you created at your Yodeck account. You can manage your groups at Yodeck by clicking the orange option at the end of the list “Manage Groups”,   or from  Account Settings > Groups, from the top right drop-down.

The second column of the list, “SAML Group Name,” is the group name displayed in your Azure account. To find the group name from your Azure Active Directory (Microsoft Entra), follow these steps:

  1. Sign in to the Microsoft Entra admin center
  2.  Identity >  Groups > All Groups

By filling up the column “SAML Group Name”, when a new user of a specific SAML group is logged in, the user will automatically inherit the permissions of the Group that the SAML group is mapping.

For example, if we want the new users of the Yodeck SAML group to be Global Administrators at the Yodeck Portal, we will make the following changes: