FIDO Device registration name encoding issue in VIP Authentication Hub
Article ID: 278839
Updated On:
Products
Issue/Introduction
In case of special characters, FIDO device registration is not recognizing these characters. In FIDO response, these characters are converting to '?'.
Sample FIDO device name ="月心dee馬zhé"
/passwordAuthenticator response (if 1st factor is PASSWORD, FIDO):
{
"flowState": "xxxxxxxxxxxxxxxxxxxx",
"userName": "xxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxx",
"credentials": [
{
"credId": "xxxxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxxxxx",
"credType": "ivr",
"credValue": "****xxxxxxxx",
"status": "ACTIVE",
"createdDatetime": "2024-01-10 06:21 AM UTC",
"modifiedDatetime": "2024-01-10 06:30 AM UTC",
"origin": "IDSTORE",
"originType": "scim",
"fidoCredIdentifierExist": false,
"domainSameAsOriginForSecurityKey": false,
"default": false
},
{
"credId": "xxxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxx",
"credType": "sms",
"credValue": "****xxxx",
"status": "ACTIVE",
"createdDatetime": "2024-01-10 06:21 AM UTC",
"modifiedDatetime": "2024-01-10 06:21 AM UTC",
"origin": "IDSTORE",
"originType": "scim",
"fidoCredIdentifierExist": false,
"domainSameAsOriginForSecurityKey": false,
"default": false
},
{
"credId": "xxxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxx",
"credType": "totp_push",
"credValue": "??dee?zhé + JPOI 2024-01-10T12:16:14.760",
"status": "ACTIVE",
"createdDatetime": "2024-01-10 09:40 AM UTC",
"modifiedDatetime": "2024-01-10 12:14 PM UTC",
"origin": "IDSTORE",
"originType": "scim",
"fidoCredIdentifierExist": false,
"domainSameAsOriginForSecurityKey": false,
"default": false
},
{
"credId": "xxxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxx",
"credType": "totp_push",
"credValue": "??dee?zhé + JPOI 2024-01-11T18:40:11.717",
"status": "ACTIVE",
"createdDatetime": "2024-01-11 01:12 PM UTC",
"modifiedDatetime": "2024-01-16 09:53 AM UTC",
"origin": "IDSTORE",
"originType": "scim",
"fidoCredIdentifierExist": false,
"domainSameAsOriginForSecurityKey": false,
"default": false
},
{
"credId": "xxxxxxxxxxxxxxxxxxxxxx",
"userId": "xxxxxxxxxxxxxxxxxxxxxx",
"credType": "totp_push",
"credValue": "???dee???\n + JPOI 2024-01-10T12:10:21.098",
"status": "ACTIVE",
"createdDatetime": "2024-01-10 06:44 AM UTC",
"modifiedDatetime": "2024-01-10 06:44 AM UTC",
"origin": "IDSTORE",
"originType": "scim",
"fidoCredIdentifierExist": false,
"domainSameAsOriginForSecurityKey": false,
"default": false
}
],
"nextaction": "FACTOR_SELECTION",
"currentFactors": [
"IVROTP",
"SMSOTP",
"PUSH"
],
"data": {
"message": "1003000",
"passwordResetURL": "https://test.example.com/default/admin/v1/PasswordUpdater"
},
"additional": {
"idpName": "XXXXXXXXX",
"idpGuid": "XXXXXXXXXXXXXXX",
"idpType": "scim",
"currentFactorLevel": 2,
"amrForCompletedFactors": [
"PWD"
],
"lastObligation": "PASSWORD"
}
}
Environment
any VIP AuthHub Release prior of 2.2.3
Resolution
This issue was identified as Defect and is fixed in 2.2.3. VIP AuthHub 2.2.3 release will be available by February 2024 second week.
Feedback
