Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 gdpr.erase60 gdpr.erase60 (gdpr.erase60)
GDPR Erase

GDPR Erase
gdpr.erase60 Member since 2020 3 posts
GDPR Erase
Posted: Jan 28, 2021
Last activity: Jan 28, 2021
Posted: 28 Jan 2021 2:53 EST
Last activity: 28 Jan 2021 4:58 EST
Closed

SAML 2.0 Authentication Fails on Multi Node cluster

We have implemented SAML 2.0 Authentication which works fine with 1 node. the moment we go multi node (2 Nodes) it fails and returns to the Login page from where SAML authentication request was initiated.

In the logs I see lot of the below errors:

Show More

We have implemented SAML 2.0 Authentication which works fine with 1 node. the moment we go multi node (2 Nodes) it fails and returns to the Login page from where SAML authentication request was initiated.

In the logs I see lot of the below errors:

2021-01-09 11:32:07,788 [tejob-executor-18753] [  STANDARD] [                    ] [                    ] ( internal.mgmt.PRRequestorImpl) INFO    - [QuiescePassivation] forcePassivateInner: passivated or destroyed requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] 2021-01-09 11:32:09,842 [    default task-134] [          ] [                    ] [                    ] (    mgmt.base.NodeRequestorMgt) INFO    - [Quiesce] Found requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] on remote node: 97815d53-4e78-48cd-81fd-f3610ec37843 2021-01-09 11:32:10,007 [    default task-134] [          ] [                    ] [                    ] (    mgmt.base.NodeRequestorMgt) INFO    - [QuiesceActivation] Requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] has been restored from passivated data as a result of quiesce 2021-01-09 11:32:10,363 [tejob-executor-18754] [  STANDARD] [                    ] [                    ] ( internal.mgmt.PRRequestorImpl) INFO    - [QuiescePassivation] forcePassivateInner: passivated or destroyed requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] 2021-01-09 11:32:26,461 [    default task-157] [          ] [                    ] [                    ] (    mgmt.base.NodeRequestorMgt) INFO    - [Quiesce] Found requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] on remote node: 97815d53-4e78-48cd-81fd-f3610ec37843 2021-01-09 11:32:26,595 [    default task-157] [          ] [                    ] [                    ] (    mgmt.base.NodeRequestorMgt) INFO    - [QuiesceActivation] Requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] has been restored from passivated data as a result of quiesce 2021-01-09 11:32:26,877 [tejob-executor-18756] [  STANDARD] [                    ] [                    ] ( internal.mgmt.PRRequestorImpl) INFO    - [QuiescePassivation] forcePassivateInner: passivated or destroyed requestor [HAQSRR961XETRX5ER1C2FOMA3R2TUD2ENA] 2021-01-09 11:32:50,234 [tejob-executor-18760] [  STANDARD] [                    ] [                    ] ( internal.mgmt.PRRequestorImpl) INFO    - [QuiescePassivation] forcePassivateInner: passivated or destroyed requestor [HF7GNG5B6WL7U6QU03F7CKEG4XA8IEPLMA]

Can anyone help with how to stop this QuiescePassivation from happening.

Show Less
***Edited by Moderator: Pooja Gadige to change content format from Discussion to Question, add platform capability tag***
To see attachments, please log in.
Pega Platform
Case Management
Security
Government
Lead System Architect

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice