We recently completed the configuration of Single Sign-On (SSO) in IrthNet using Microsoft OpenID. While the integration is functioning as expected, we have noticed that users are still able to authenticate using their local IrthNet username and password even after SSO has been enabled.
We would like to inquire whether IrthNet supports enforcing Microsoft (OpenID) authentication at the individual user level. Specifically, we are considering a model where:
When a new user account is created, local authentication remains enabled so the user can log in initially and complete the association with their Microsoft account.
After the Microsoft account has been successfully linked, an administrator can update a user-level setting to require Microsoft (OpenID) authentication only, thereby preventing subsequent logins using local credentials.
Could you please let us know if this type of functionality is currently available in IrthNet? If not, we would appreciate your guidance on any recommended or supported approaches to enforce SSO-only authentication for selected users, while still allowing local authentication for initial onboarding or administrative access.
We recently completed the configuration of Single Sign-On (SSO) in IrthNet using Microsoft OpenID. While the integration is functioning as expected, we have noticed that users are still able to authenticate using their local IrthNet username and password even after SSO has been enabled.
We would like to inquire whether IrthNet supports enforcing Microsoft (OpenID) authentication at the individual user level. Specifically, we are considering a model where:
Could you please let us know if this type of functionality is currently available in IrthNet? If not, we would appreciate your guidance on any recommended or supported approaches to enforce SSO-only authentication for selected users, while still allowing local authentication for initial onboarding or administrative access.
Thank you for your assistance.
0 Votes
0 Comments
Login or Sign up to post a comment