-
Notifications
You must be signed in to change notification settings - Fork 0
Updae secure signals client server integrations fix #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updae secure signals client server integrations fix #60
Conversation
| // Safety net: If token exists but Secure Signals haven't loaded yet, reload the page | ||
| if (token && !secureSignalsStorage) { | ||
| console.log("Token exists but Secure Signals not loaded yet, reloading page..."); | ||
| location.reload(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added just in case secure signals doesnt load properly with delay
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also added condition to not reload on opt-out since the token wouldnt be generated
| } | ||
| <% } else if (isOptout) { %> | ||
| // Opt-out case - set identity to null | ||
| sdk.setIdentity(null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think we should have to do this? the sdk should already take care of the optout identity
Summary of changes/key takeaways: