Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Via SAML and LDAP, lockout features are supported. There is an opportunity to provide a lockout message from the Sametime interface when this condition is provided by the authentication service, which is in consideration.
Starting with Sametime 12, Sametime only supports a configuration based on an LDAP directory service. It's therefore unlikely, that HCL will create any enhancements for a native Domino directory based configuration in Sametime 11.
You can configure Sametime 11 for SSO between a SAML identity provider and the Sametime Community Server. In such a scenario Sametime does not do the authentication. Instead it relies on a token (SAML assertion) received from the IDP. That should allow you to implement whatever lockout option your SAML IDP supports. https://help.hcltechsw.com/sametime/11.0.0/admin/enabling_sso_saml.html
Yes., but if using LDAP is the situation any better? meaning does Domino have a lockout feature for LDAP?
Are you referring to a Sametime 11 environment with native Domino directory integration (i.e. ST is NOT configured to use LDAP) ?