Question 1 Replies 38 Views × Close popover Bin Xu (GAVINHSU) Mediatek Inc. China Mediatek Inc. China CN View Profile Send Message GAVINHSU Member since 2011 24 posts Mediatek Inc. China Posted: August 12, 2020 Last activity: September 10, 2020 Posted: 12 Aug 2020 20:47 EDT Last activity: 10 Sep 2020 1:33 EDT Solved Need to know about the how PEGA manages OAuth 2.0's token Hi, We're planning to implement OAuth 2.0 recently, and generally PEGA will act as the client. Before the implementation, we still have some questions need to be figured out: We have cluster running with PEGA platform, will the token shared between individual server nodes? Or each node has its own token? How PEGA knows the token is expired? Is there any way we can maintain the expiration time? What will happen if PEGA detects that the token expired? Can we have our own handler of the token expire event? Any other information about the OAuth 2.0 would be appreciate. Thanks very much. ***Edited by Moderator: Pallavi to change content type from Discussion to Question*** Pega Platform 8.3.1 Data Integration Manufacturing System Architect × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Accepted Solution Posted: 7 months ago Updated: 7 months ago Posted: 10 Sep 2020 1:10 EDT Updated: 10 Sep 2020 1:33 EDT × Close popover Bin Xu (GAVINHSU) Mediatek Inc. China Mediatek Inc. China CN View Profile Send Message GAVINHSU Mediatek Inc. China replied to GAVINHSU Turns out the tokens are shared between all server nodes, and the expiration time is controlled by token server. PEGA will try to get another token if the previous one was marked as expired.