Skip to content
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

Transaction for 3rd party auth process #1572

Open
edwardyoon2 opened this issue Jan 20, 2025 · 0 comments
Open

Transaction for 3rd party auth process #1572

edwardyoon2 opened this issue Jan 20, 2025 · 0 comments

Comments

@edwardyoon2
Copy link

I expected that I can track a transaction for 3rd party social login like below:

const currentTransaction = apm.getCurrentTransaction();
const redirectUrl = `${authUrl}?elasticTxId=${currentTransaction.id}`;

// 3rd party callback redirects
const txId = urlParams.get('elasticTxId');
apm.startTransaction('auth-callback', 'auth', {
  childOf: txId
});

But, it seems impossible to maintain transaction state across cross-domain redirects.
Is there some reason about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant