IDP-2.4.0 & 3.1.1authentication request -Behavior for HTTP & HTTPS - Same browser

[Surinaidu Majji]

We are working with Java application which is mainly dependent on Cookies.
We are facilitating our
users to access application with both "HTTP" and "HTTPS".

Our Requirment::
We need is to treat application users  with "HTTP" and "HTTPS" differently.
Hence if the user access the application with "HTTPS" in one tab of the
browser and the user access through "HTTP" in another tab of the same
browser  need to be treated as different users.


Earlier we were using Shibboleth-IdentityProvider-2.4.0 and the following
was the behaviour.
- Open application using https://<<ipaddress>>:<<port>>/myApp in one tab.
- Sending authentication request to shibboleth IDP.
- Gives login page.
- Enter the credentials and access the requested application.

 - Open application using http://<<ipaddress>>:<<port>>/myApp in another
tab.
- Since user is different(HTTP), Sending authentication request to again to
shibboleth IDP.
- Gives login page.
- Enter the credentials and access the requested application.

In the above scenario both the cases(HTTP and HTTPS) treated as different.
Shibboleth-IDP(2.4.0) treated differently when browser sending
authentication request. The same browser is sending authentication request
2 times with different tabs but IDP considered both are different users and
gives login page.

Now we are using Shibboleth-IdentityProvider-3.1.1 and the following is the
behaviour.
- Open application using https://<<ipaddress>>:<<port>>/myApp in one tab.
- Sending authentication request to shibboleth IDP.
- Gives login page.
- Enter the credentials and access the requested application.

 - Open application using http://<<ipaddress>>:<<port>>/myApp in another
tab.
- Since user is different(HTTP), Sending authentication request to again to
shibboleth IDP.
- Gives SAML response to  Service Provider URL (configured URL to receive
authentication response) indicating that this  user has
authenticated(Instead of giving login page)
- Application is crashing because we are treating both are different but
shibboleth-IDP-3.1.1 treating as only one user.

Here are my queries:
1) May I know, On what basis shibboleth-IDP(3.1.1) treating as Same unlike
shibboleth-IDP2.4.0?
2) Kindly suggest, How to achieve our requirement(HTTPS & HTTP different)
with IDP-3.1.1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151123/4913287c/attachment.html>