Aggregate Verifier use, is this the right config?

[kiemmisouksingmoneso]

loginConfig: {
auth0github: {
verifier: “ANKIT1”, // Pass the Verifier name here. eg. w3a-agg-example
verifierSubIdentifier: “auth0-github”, // Pass the Sub-Verifier here. eg w3a-a0-github
typeOfLogin: “jwt”, // Pass the type of login provider. For Auth0, it’s jwt and not Auth0.
clientId: “PASS THE ID HERE”, // Pass the Auth0 Client ID here.
},
secondauth0github: {
verifier: “ANKIT1”, // Pass the Verifier name here. eg. w3a-agg-example
verifierSubIdentifier: “auth0-github”, // Pass the Sub-Verifier here. eg w3a-a0-github
typeOfLogin: “jwt”, // Pass the type of login provider. For Auth0, it’s jwt and not Auth0.
clientId: “PASS THE 2nd ID HERE”, // Pass the Auth0 Client ID here.
},
}

[Ayush]

Hey @kiemmisouksingmoneso, can you please provide information so we can help you?

[maharshi]

@kiemmisouksingmoneso Hey, with aggregate verifiers, it’s not the client id that varies. Because client IDs are particular to a project and aggregation of them is something that we do not support as of yet. An aggregate verifiers has sub-verifiers which are aggregated based on a field, let’s say email. So they give same address regardless of different login methods as per the different subverifiers as long as the email used to log in is the same. So here, instead varying client id you vary the verifiersubIdentifier field.
Please read more about aggregate verifiers here.