How consistent is `aggregateVerifier` field of getUserInfo()?

[antonio]

Hi all,

Our platform utilizes the aggregateVerifier to keep track of the user’s logged in method. From the JWT we can decode for keys like tkey-auth0-email-passwordless-lrc or tkey-google-lrc that allow us to determine the auth method.

We did notice that on mainnet the passwordless key for example is tkey-auth0-email-passwordless-cyan. This sitll works for us as we can use regex on “passwordless” or something to determine this was logged in via email passwordless.

My question is, how reliable are these keys and will a regex method like what we did be consistent enough in the future as well?

[vjgee]

@antonio Thanks for your recent communication.

Your request has been forwarded to our Dev team and we will get back with further updates.

[antonio]

hey @vjgee. Is there an update here?

[shahbaz]

Hi @antonio

@antonio

how reliable are these keys and will a regex method like what we did be consistent enough in the future as well?

These are reliable as these are our default verifiers that will not change. But to determine the auth method, you can look for the typeOfLogin field from the getUserInfo function.