You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Authenticating with OpenID Connect

Pulse configures Spring to authenticate the user by delegating authentication to an OpenID Connect Provider (OP). PlantUML 1.2023.12 <b>This version of PlantUML is 303 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 8) ] @startumltitle Pulse Authenticates with OpenID Connect Provider (OP)title Pulse Authenticates with OpenID Connect Provider (OP)participant User as userparticipant Browser as browserparticipant "Pulse (Spring)" as springparticipant OP as opuser -> browser +: /<protected-uri>Syntax Error?

Authorizing With Access Tokens

During authentication, Pulse requests an access token along with the ID token. Internally, Pulse uses the access token to connect to the Geode cluster's JMX manager. PlantUML 1.2023.12 <b>This version of PlantUML is 303 days old, so you should<b>consider upgrading from https://plantuml.com/download [From string (line 11) ] @startumltitle Pulse Connects to Geode JMX with the User's Access Tokentitle Pulse Connects to Geode JMX with the User's Access Tokenparticipant "Pulse Page\nJavascript" as pageparticipant "Pulse\nController" as pulseparticipant Repository as repositoryparticipant Spring as springparticipant Cluster as clusterparticipant "Geode JMX" as jmxparticipant "Custom\nSecurity\nManager" as smpage -> pulse +: /<some-data-url>Syntax Error?

Refreshing Expired Access Tokens

If the OP issues a refresh token, Pulse attempts to refresh the user's access token when it expires.

Automatic Disconnect and Logout When Unable to Refresh

If there is no refresh token, or if the refresh token has expired, or if the OP declines to refresh the expired access token, Pulse disconnects from the JMX manager and logs the user out of the Pulse browser session.

  • No labels