[JIRA] (IDP-1859) strange IDP SSO session
Hong Ye (Jira)
jira at shibboleth.atlassian.net
Fri Aug 27 13:17:00 UTC 2021
Hong Ye ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A00a92469-174a-4a39-aeba-4b46d2cb20be ) *commented* on IDP-1859 ( https://shibboleth.atlassian.net/browse/IDP-1859?atlOrigin=eyJpIjoiMzk4NDNjNjI5YzA5NGY4MWEyMWU4Yzg0MWFmYjUyODMiLCJwIjoiaiJ9 )
Re: strange IDP SSO session ( https://shibboleth.atlassian.net/browse/IDP-1859?atlOrigin=eyJpIjoiMzk4NDNjNjI5YzA5NGY4MWEyMWU4Yzg0MWFmYjUyODMiLCJwIjoiaiJ9 )
Hi Scott,
Could you let me know how to access member project for support?
Thanks,
Hong
On 8/27/21, 8:49 AM, "Scott Cantor (Jira)" <jira at shibboleth.atlassian.net> wrote:
[ https://shibboleth.atlassian.net/browse/IDP-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31319#comment-31319 ]
Scott Cantor commented on IDP-1859:
-----------------------------------
This isn’t really a bug report. If you’re looking for support, please use the member project for that and you would need to attach the actual logs. The audit log is not going to help diagnose anything about how the IdP is behaving, and generally “I had to log in” won’t show up in any log because it’s indicative of the absence of a session, which isn’t really all that visible.
> strange IDP SSO session
> -----------------------
>
> Key: IDP-1859 ( https://shibboleth.atlassian.net/browse/IDP-1859 ) Closed
> URL: https://shibboleth.atlassian.net/browse/IDP-1859
> Project: Identity Provider
> Issue Type: Task
> Components: Configuration
> Affects Versions: 4.0.1
> Reporter: Hong Ye
> Assignee: Scott Cantor
>
> Hello,
> In idp.properties, I have
> idp.session.timeout = PT10H
> idp.authn.defaultLifetime = PT10H
> idp.authn.defaultTimeout = PT10H
> With this setting, I think in the same browser, I just need to login to IDP once. then I'll have active IDP session for 10 hours. With active IDP session, I won't be prompted for login when accessing other websites as long as that site doesn't require forceAuth. I did some testing, I can't explain the behavior. Here is my test:
> 1. Accessed whoiam.cornell.edu which has shbboleth SP installed
> 2. Prompted for login at Cornell IDP. Logged in
> 3. whoiam.cornell.edu displayed to me.
> 4. Deleted shibSession cookie at whoiam.cornell.edu domain. Then refresh whoiam.cornell.edu. I wasn't prompted for login, SSO worked for me. Deleted shibSession cookie again, refresh whoiam.cornell.eud, I was prompted for login. I don't understand why the second time I was prompted for log in. Do I miss anything in IDP
> configuration?
> Here is IDP audit log:
> 2021-08-26T20:32:23.028-0400|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|https://www.whoiam.cornell.edu/shibboleth|http://shibboleth.net/ns/profiles/saml2/sso/browser|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|urn:oasis:names:tc:SAML:2.0:status:Success|||false|hy93|https://refeds.org/profile/mfa|
> 2021-08-26T20:32:59.698-0400|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|https://www.whoiam.cornell.edu/shibboleth|http://shibboleth.net/ns/profiles/saml2/sso/browser|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|urn:oasis:names:tc:SAML:2.0:status:Success|||true|hy93|https://refeds.org/profile/mfa|
> 2021-08-26T20:35:28.176-0400|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect|https://www.whoiam.cornell.edu/shibboleth|http://shibboleth.net/ns/profiles/saml2/sso/browser|urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST|urn:oasis:names:tc:SAML:2.0:status:Success|||false|hy93|https://refeds.org/profile/mfa|
> Thanks,
> Hong
–
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100175)
( https://shibboleth.atlassian.net/browse/IDP-1859#add-comment?atlOrigin=eyJpIjoiMzk4NDNjNjI5YzA5NGY4MWEyMWU4Yzg0MWFmYjUyODMiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/IDP-1859#add-comment?atlOrigin=eyJpIjoiMzk4NDNjNjI5YzA5NGY4MWEyMWU4Yzg0MWFmYjUyODMiLCJwIjoiaiJ9 )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175- sha1:6c2908d )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20210827/2954bb6c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-da6d3544-d930-4a0f-a6f0-8b603a5623a3
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20210827/2954bb6c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-d43da6b4-26a9-4a7a-a427-ca07a9edbf6d
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20210827/2954bb6c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-764c172e-f9ba-4872-9042-48c72ff7f2a0
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20210827/2954bb6c/attachment-0005.png>
More information about the commits
mailing list