While the admin dashboard allows you to define requirement for Terms of Service acknowledgement in System->Registration->"Require users to accept the Terms of Service", it also notes that this is not required if SSO is implemented.
We have SSO enabled, but are still looking to leverage the Terms of Service within Lithium - should this work by design? I tested this with a new user registering via SSO, but they were not presented with the ToS. Is this a bug, or a designed intent?
Alternatively you could add a custom component to the UserSsoRegistrationPage page layout. That's the page shown after returning from the SSO login call where new members are asked to complete their profile by picking a community name. In this component you could expose the page.user_signup.terms_of_service text string next to a checkbox which would enable the form submission button when checked.
Out of curiosity: What creates the requirement to agree to additional ToS on top of the one already signed on SSO account creation? Most of our customers reviewed their account terms and conditions and found that the sections on content ownership and allowed use covered community scenarios as well.
Thanks! This might just be my Plan B. The reasoning for differentiation is strategic - I can expound a bit more once launch is complete, but there's definitely a sound set of reasons why we want/need to have the separation; I'm all for the umbrella/hierarchical approach where it can inherit appropriately, and it would definitely make things simpler if that was the case. 🙂