Federation and Single Sign On (SSO)

kubeark offers a variety of capabilities for single sign on (sso) and social logins, making it easy to integrate with popular identity providers such as google and facebook with sso, users can sign in once and access multiple applications without having to repeatedly enter their credentials this is not only convenient for users, but also helps improve security by reducing the number of passwords users need to remember kubeark allows users to authenticate with their existing social media accounts instead of creating new credentials this makes it easy for users to get started with your application and can help increase user engagement how to enable? step 1 on the main kubeark page, go to user management and select users from the users page, on the top left corner of the workspace, select idp step 2 this will take you to the user interface of the identity management console from the top right corner of the screen, select admin interface the kubeark identity console presents two different views, which are determined by the role of the user who is accessing them user interface this is the default screen for user accounts admin interface this is the identity management console dedicated to organization admins step 3 within the admin interface , go to directory > federation & social login step 4 here you will see a list of all active sources of identities to enable a new identity provider, select create step 5 choose your preferred source from the list of available providers and click next step 6 in the source configuration prompt, enter all details required for configuring the new source depending on your previous selection when configuring federation and social login, it is important to keep in mind that the detailed configuration process may vary depending on the specific identity provider being used for example, if you are integrating with azure ad, you will need to follow the respective steps to enable the service from the azure portal similarly, other identity providers may require different steps or configurations therefore, it is recommended to refer to the official documentation or support resources provided by the identity provider to ensure that the necessary configuration is completed correctly by following the provider specific guidelines , you can ensure a smooth and secure integration between your application and the identity provider