custom authentication

[Virajitha Sarma]

Hi,

I have a web application(SAML enabled serviceprovider) with its own login
page. I have also configured IDP that can provide SSO functionality.
Instead of using the IDP login page, I want to use my web applications
login page for taking in user credentials and authentication.
I came across this resource which talks about the same requirement. But the
solution provided is not very clear.
https://lists.internet2.edu/sympa/arc/shibboleth-users/2008-07/msg00704.html

solution copied from the URL:
I have done similar implementation here and you might find it useful.
I modified Remote authentication by using the concept of UserPassword
authentication.

1. Implement a servlet (or similar) on legacy web application and have
it protected by legacy authentication mechanism.

2. On shibboleth IDP, Redirect user to legacy web application's
protected servlet. Protected servlet will insure that the login happens
first.
>>> In IDP, where does this configuration go.

3. After successful authentication, protected servlet opens back channel
HTTPS connection to pass user profile to IDP and then redirects user
back to IDP's RemoteUser endpoint.
>>>there are 2 points here: 1. send user profile to IDP
and 2. redirects user back to IDP's RemoteUser endpoint
Are these actions carries out so that IDP can maintain a user
session?
When I try to access Remoteuser end point I am getting "No
conversation key found". I am not able to find any documentation
on what is the conversation key?
Could you please provide some inputs on this?

In the whole conversation between legacy web and IDP, a unique one time
session key and return URL were the key factors to relate all the
communication.

-Anurag Sharma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161031/08da7c0e/attachment.html>