custom authentication

[Virajitha Sarma]

Hi Scott,

Your comments have answered most of my queries. Thank you so much.

> All the applications (not shibboleth SP's but support SAML) trying to
achieve
> SSO using Shibboleth IDP( based on SAML) should have only common login
> parameters like username and password for authentication?

Sorry I was not clear before. By "parameters", I meant that if I were to
use IDP login page, then only username and password would be given for
authentication. For any additional input login parameters, relaytoken will
be used. Please confirm.


Regards,
Virajitha



On Tue, Nov 1, 2016 at 6:56 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > All the applications (not shibboleth SP's but support SAML) trying to
> achieve
> > SSO using Shibboleth IDP( based on SAML) should have only common login
> > parameters like username and password for authentication?
>
> The applications have *no* parameters for authentication. They have
> nothing to do with the process. They issue a SAML request. That's it. That
> does not include a name or a password.
>
> > The reason I am  asking this is, my web application requires additional
> parameter say a
> > "location" for login.
>
> Anything your application needs to recover afterwards has to be saved off
> and bound to a RelayState token. You send the RelayState parameter along
> with the SAML request and the IdP will return it in the form response back.
>
> If you want to use SAML you need to deploy an existing SAML SP package,
> Shibboleth or otherwise. It handles all these issues for you.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 

Regards,
Virajitha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161101/a9c73666/attachment.html>