When the rubycas server tries notifying the consumers about a log out, one or more of those consumers may be down.
Surely there should be a policy for retrying those? e.g. every 4 hours, perform the SSO requests to those servers again. State about pending logouts would be persisted to the DB until resolved.
Alternatively, a programmer-defined policy could decide if and when the consumers should be notified again.
When the rubycas server tries notifying the consumers about a log out, one or more of those consumers may be down.
Surely there should be a policy for retrying those? e.g. every 4 hours, perform the SSO requests to those servers again. State about pending logouts would be persisted to the DB until resolved.
Alternatively, a programmer-defined policy could decide if and when the consumers should be notified again.
What do you think?
Thank you - Victor