Attachment screen getting stale after 10-15 mints of inactivity for sso operator
Hi All,
From my sso operator when I upload a document to pega but wait for 15 mints before clicking the attach button
I am getting below pop-up message
I am not facing this issue when I login with normal pega operator any idea on why this happens , and how to avoid it?
Thank you
Pegasystems Inc.
GB
@malliswar We may need more details whether you are using OOTB attachment functionality.
Can you confirm whether you see an Access Group timeout? Are you using OpenID?
The ODIC logoff deletes Pega-RULES cookie and should re-direct to the login screen if using oAuth0 OpenID IDP for OIDC sso login and using Access group time out for log off. If Log off is happening after timeout it should be of redirecting to Log in page.
This has been logged as a future enhancement request under US-387760 .
is there a change in behaviour if you configure a pxsession timer solution?
Note that the Authentication timeout for a Mashup would be part of the AuthService you are using. On the custom tab there is a check box for "Use PegaRULES timeout". When checked the AccessGroup timeout value is then used. When a user is idle for the amount of time specified in the AccessGroup timeout field and an request is made the timeout activity is run first.
Note: Authentication idle timeouts with a mashup get a bit tricky as these are embedded in a top level application via an Iframe. Our timeouts and the top level application timeouts might be different. Working in the top level application doesn't reset our idle timeout and working within the PRPC Iframe doesn't reset the top level application idle timeout.
@malliswar We may need more details whether you are using OOTB attachment functionality.
Can you confirm whether you see an Access Group timeout? Are you using OpenID?
The ODIC logoff deletes Pega-RULES cookie and should re-direct to the login screen if using oAuth0 OpenID IDP for OIDC sso login and using Access group time out for log off. If Log off is happening after timeout it should be of redirecting to Log in page.
This has been logged as a future enhancement request under US-387760 .
is there a change in behaviour if you configure a pxsession timer solution?
Note that the Authentication timeout for a Mashup would be part of the AuthService you are using. On the custom tab there is a check box for "Use PegaRULES timeout". When checked the AccessGroup timeout value is then used. When a user is idle for the amount of time specified in the AccessGroup timeout field and an request is made the timeout activity is run first.
Note: Authentication idle timeouts with a mashup get a bit tricky as these are embedded in a top level application via an Iframe. Our timeouts and the top level application timeouts might be different. Working in the top level application doesn't reset our idle timeout and working within the PRPC Iframe doesn't reset the top level application idle timeout.
https://collaborate.pega.com/question/how-change-timeout-requestors-using-iac-authentication
If you need further help with this it might be best if you log a support incident for this:
If you need an in-depth analysis of what might be occuring in your scenario I suggest you log a support incident. For the support team please provide the following information:
- Network trace for the issue
- Console log error if any
- Error/Issue screenshot
Please can you provide the INC number here so that we can help you track it?