microscopic-answer-24504
03/20/2023, 4:01 PMdamp-car-18231
03/20/2023, 4:06 PMupdateIdentityBody := oryclient.UpdateIdentityBody{
Credentials: &oryclient.IdentityWithCredentials{
Oidc: &oryclient.IdentityWithCredentialsOidc{
Config: &oryclient.IdentityWithCredentialsOidcConfig{
Providers: []oryclient.IdentityWithCredentialsOidcConfigProvider{
oryclient.IdentityWithCredentialsOidcConfigProvider{
Provider: "microsoft",
Subject: azureUser.Id,
},
},
},
},
},
SchemaId: orySchemaId,
State: oryclient.IDENTITYSTATE_ACTIVE,
Traits: map[string]interface{}{
"email": azureUser.Mail,
"name": map[string]string{
"first": azureUser.GivenName,
"last": azureUser.Surname,
},
},
}
damp-car-18231
03/20/2023, 4:09 PMsubject_source: "me"
settingdamp-car-18231
03/20/2023, 4:28 PMbland-eye-99092
03/20/2023, 5:37 PMdamp-car-18231
03/20/2023, 5:51 PMDelete an identity credential by its type You can only delete second factor (aal2) credentials.
bland-eye-99092
03/20/2023, 5:53 PMdamp-car-18231
03/20/2023, 5:54 PMdamp-car-18231
03/20/2023, 6:03 PMdamp-car-18231
03/20/2023, 7:10 PMEach credential - regardless of its type - has one or more identifiers attached to it. Each identifier is universally unique. Assuming we had one identity with credentials
credentials:
password:
id: password
identifiers:
- <mailto:john.doe@acme.com|john.doe@acme.com>
and tried to create (or update) another identity with the same identifier (<mailto:john.doe@acme.com|john.doe@acme.com>), the system would reject the request with a 409 Conflict state.
It’s coming from an unique constraint in identifierdamp-car-18231
03/20/2023, 7:20 PM