SAML response mapping to addHumanUser field
š¬Self-hostedāQuestionāUnsolved
hello Team,
For the : https://$CUSTOM_DOMAIN/v2/idp_intents/:idpIntentId
[https://zitadel.com/docs/apis/resources/user_service_v2/user-service-retrieve-identity-provider-intent]
The response contains addHumanUser,
which is standard mapping for the oauth IDP like Google and Microsoft. Where I get the below as standard response:
"profile": {
"givenName": "Minnie",
"familyName": "Mouse",
"nickName": "Mini",
"displayName": "Minnie Mouse",
"preferredLanguage": "en",
"gender": "GENDER_FEMALE"
},
However in case of SAML, is the mapping managed by Zitadel or we need to have the mapping done based on the attributes ? As SAML response can have different naming for the fields
For the : https://$CUSTOM_DOMAIN/v2/idp_intents/:idpIntentId
[https://zitadel.com/docs/apis/resources/user_service_v2/user-service-retrieve-identity-provider-intent]
The response contains addHumanUser,
which is standard mapping for the oauth IDP like Google and Microsoft. Where I get the below as standard response:
"profile": {
"givenName": "Minnie",
"familyName": "Mouse",
"nickName": "Mini",
"displayName": "Minnie Mouse",
"preferredLanguage": "en",
"gender": "GENDER_FEMALE"
},
However in case of SAML, is the mapping managed by Zitadel or we need to have the mapping done based on the attributes ? As SAML response can have different naming for the fields
