I want to make “terms of service” and “privacy policy” a clickable link. Linking to the corresponding page of those terms. What is the point of showing this text if the user cannot see which terms he is agreeing to? Also why is it not possible to add terms of service texts to the new modern login page?
It would be also helpful if someone could tell me how to add a GDPR consent checkmark that is required to initiate the buttons of the login.
I understand that you would like to know how to customize the privacy policy text on your custom login page.
To make the text a clickable link, you will need to make changes to the LanguageDictionary object in your custom Universal Login Page to define a hyperlink. See below for an example:
languageDictionary: {
signUpTerms: "I agree to the <a href='/terms' target='_new'>terms of service</a> and <a href='/privacy' target='_new'>privacy policy</a>."
},
mustAcceptTerms: true,
Moreover and, unfortunately, only the Classic Universal Login Page allows for Terms of service text to show on the login page. Our New Universal Login vs. Classic Universal Login documentation emphasizes these limitations.
As for GDPR Consent tracking, I recommend using an Action to accomplish this. See the GDPR: Track Consent with Custom UI documentation to learn more.
If you have any questions about the implementation, please feel free to reach out. I would be happy to help!
It works on the Sign up section but on the “Log In” section I can click “Sign in with google” and create a new account without having to click the checkbox or even ever seeing it.
What you have observed with the “Sign in with Google” button is normal behavior. And unfortunately, there is not much you can do to prevent Social Connections from logging in.
After discussing this with my colleague, one option is to use a Post-Login Action to deny these Social users from logging in until they have signed up to your app and accepted your privacy policy.
An alternative option is to use a Redirect Action to redirect your users who are logging in for the first time to another page to accept your privacy policy. Once they have accepted the terms, they can resume authentication as usual. This way, you can capture cases where Social users can log in without signing up and agreeing to your privacy policy.