Skip to content

Transaction for 3rd party auth process #1572

@edwardyoon2

Description

@edwardyoon2

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions