Custom Sign-In Pages HELP!

[dogmai_]

My organization wants me to add a checkbox to my sign-in page that users must select before they are able to login. This is because they want to post some user agreement text that has to be agreed to prior to gaining access but I am stumped... Adding the checkbox has been the easy part but I haven't been able to figure out how to prevent users from signing in if it is unchecked. What's worked for me on test pages hasn't translated nicely to the loginpage.thtml. I would appreciate any suggestions.

Thanks!

[EdBradshaw_]

We've been doing this for a while now.

Download the sample sign-in page files. Open LoginPage.thtml and create an Acceptible Use page, using HTML. You can get rid of all the login forms and start from scratch. You just need to include two things.

The header: <%# NetScreen Page Version 1002 %> (this will change from version to version, so you need to update the file each time)

And a pointer to the login page, eg. <input onClick="location.href = '../../../login'" tabindex=1 type=button value=" I Agree ">

notice the '../../..', this is to bring you back to the proper URL location from dana-na/auth/...etc.

Zip everything back up and upload. When you upload the custom page, I would check "skip validation checks"

I create two sign-in policies. The first for */ will have the custom AUP as the sign-in page. The second will be a */login that will use the default login page. When the user clicks on the "accept" button, they are redirected to https://yoursite.com/login

For added security, I create a NULL auth-realm with no role mapping. I use this NULL realm for the AUP sign-in policy.

We go one step further and created a choice page that lets users choose full access or just OWA email for ease and speed.

Ed Bradshaw

[dogmai_]

I don't think that this solution will work for my purposes... I have probably 20 different login URLs and if I am understanding correctly, I would have to create a separate realm/signin for each one that splashes the agreement and then redirects them to the correct login page... I was hoping more for a simple checkbox on the actual sign-in web page that, left unchecked, would prevent users from signing in.

If I've misunderstood you, I apologize.

Thanks!

Jason

[kenlars_]

Would it work to change the "Sign In" button on the sign-in page to read "I accept this user agreement" and modify the page to include the agreement between the username/password fields and the button?

Alternatively, could you use the onSubmit event handler to determine if the checkbox was checked, and return true only if it was. I'm certainly not a Javascript expert, but it looks like you could do that, and maybe even find a way to display a message if the checkbox had not been checked.

[dogmai_ · Accepted solution]

I got a little help from advanced JTAC support with this one (it was a 'best effort' kind of recommendation but the customizations are not supported if I run into problems)...

Once I added this code, zipped the customized template back up and then applied it to a sign-in page, I got the results that I needed.

I passed the suggestion about moving the submit button below the agreement and changing it's text to 'I agree......' through management (seemed like a simple enough and a good solution to me) and they decided that they wanted a more intentional action from our users like the checkbox requirement before login.

Thanks for the replies!