We usually don't have a lot of options to speed up SSO. There is a java option for tomcat (maxpacketsize) that forces TCP [page 12|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/002b818d-3db2-2b10-9895-c7b5fd4cbc71]. This setting can improve SSO performance by eliminating failed UDP attempts (kerberos default).
The doc also indicates how to troubleshoot SSO issues. When SSO is enabled the tomcat server basically sends 401 to all users attempting to hit the infoview URL. SSO is then a process initiated by the browser between the client maching and DC (called spnego). So usually SSO slowness has to be troubleshot as a Microsoft issue. On the BO side once credentials are sent to the CMS then authorization occurs (if the CMS is having trouble looking up group info then the problem would likely be with BO).
You can open a support case and have an authentication engineer help you if needed.
Regards,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.