Invalid_request: No attribute was found to generate the nameIdentifier. We tried with:

Help
,
1

Hello

I am configuring the Jenkins Plugin SAML Single Sign On(SSO), but I have the error where it seems that the login attribute does not exist.

Here is the error:

{
“date”: “2024-02-12T18:17:06.090Z”,
“type”: “f”,
“description”: "No attribute was found to generate the nameIdentifier. We tried with: ",
“connection”: “xxxxxxxxxx”,
“connection_id”: “xxxxxxxxxxxxxxyytV1qjF7U2F”,
“client_id”: “xxxxxxxxxxxxxxxhqH9OIeqaXPSFWT”,
“client_name”: “xxxxxxxxxx”,
“ip”: “xxx.xxx.xxx.xxx”,
“user_agent”: “Edge 121.0.0 / Windows 10.0.0”,
“details”: {
“body”: {},
“qs”: {
“state”: “xxxxxxxxxxxxbBhwBKssIuYFiFdh1L”
},
“connection”: “xxxxxxx”,
“error”: {
“message”: "No attribute was found to generate the nameIdentifier. We tried with: ",
“oauthError”: “invalid_request”,
“type”: “request-error”
},
“session_id”: “xxxxxx_cQx2s7EU6O-TDzH1UAq3Bmf0TnYT”,
“stats”: {
“loginsCount”: 89
}
},
“hostname”: “xxxxxxx.us.auth0.com”,
“strategy”: “xxxxxxxx”,
“strategy_type”: “xxxxxx”,
“log_id”: “90020240212181706143552000000000000001223372063907587218”,
“_id”: “90020240212181706143552000000000000001223372063907587218”,
“isMobile”: false,
“id”: “90020240212181706143552000000000000001223372063907587218”
}

Thanks by support.

2

Hi Giovanni,

Thanks for reaching out. This is Matias, I’m a Developer Support Engineer from Auth0, and I will be glad to help you with this issue.

I tried to replicate the issue, and after I installed and configured the SSO integration for the first time, everything worked as expected. There is no option in the UI to make changes to the SAML addon for the SSO integration, but I can see that “nameIdentifierProbes” was set to the following array:
“nameIdentifierProbes”: [
“http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier”,
“http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name”,
“http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress”
]

However, once I made a change to the SSO integration (simply changed the Callback URL, which is one of the two parameters you can change), the integration stopped working and I received the same error "No attribute was found to generate the nameIdentifier. We tried with: ". This is because “nameIdentifierProbes” was set to an empty array .

I’ve escalated this bug to Engineering so that they are aware of it and can implement a fix. But in the meantime, you can fix your implementation in one of two ways:

  1. You can delete your ‘Jenkins’ SSO integration and create a new one with the right Callback URL, remember that if you make any changes to the integration afterwards, it will break. Also, keep in mind that some of the configuration values in the Tutorial tab will change.

  2. You can update the SSO integration using the Auth0 Management API (PATCH /api/v2/clients/{id}) to fix it. These are the steps you would need to follow:
    Use the Management API endpoint mentioned here: Auth0 Management API v2
    You can get the Client ID for this SSO integration in the Auth0 Dashboard > Applications > SSO Integrations > Jenkins > You will see the Client ID on top, below the name.
    Use the following body in the PATCH request to fix your implementation:

{
  "issuer": "urn:TENANT-NAME",
  "mappings": {},
  "createUpnClaim": true,
  "passthroughClaimsWithNoMapping": true,
  "mapUnknownClaimsAsIs": false,
  "mapIdentities": true,
  "signatureAlgorithm": "rsa-sha1",
  "digestAlgorithm": "sha1",
  "lifetimeInSeconds": 3600,
  "signResponse": false,
  "typedAttributes": true,
  "includeAttributeNameFormat": true,
  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified",
  "nameIdentifierProbes": [
    "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
    "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name",
    "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"
  ],
  "authnContextClassRef": "urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified",
  "logout": {
    "slo_enabled": true
  },
  "binding": "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
}

Replace TENANT-NAME with the name of your Auth0 tenant.

If you eventually need to change the Callback URL again, you can PATCH the SSO integration again with the above body.

Cheers!

3

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.