🔓Direct SSO Login to Forms

You setup SSO and use it for your person records. You know your students can access their application using your institution's single sign-on authentication.

And you may be aware of the Knowledge Base's recommended URL structure to use SSO login for a person/application portal. And you know you can require login for a form using Form Properties – but can you require SSO login on a form?

The short answer is – no, you cannot require SSO login. Slate username/password authentication and secure link will technically be enabled, too.

But you can use the same Single Sign-on URL structure referenced in the KB to hand off authentication to single sign-on; not just to portals, but to any person or application scoped form in Slate. And so long as you never publish the “normal” Slate URL, then you can effectively “require” SSO login for those forms.

Anytime you use the ?realm=&r= URL structure, you are directing Slate to initiate an authenticated session using SSO, and the user will remain logged in for subsequent portal or form navigation, too.

We recommend using encoded URL equivalents of symbols in your URL path, rather than just appending the path directly in the &r= structure. This improves the reliability of the transition from SSO authentication back to the redirected URL.