# Autodesk SSO on Auth0

**URL:** <https://community.auth0.com/t/autodesk-sso-on-auth0/199814>\
**Category:** Get Help\
**Tags:** application, sso\
**Created:** [May 11, 2026, 1:46pm UTC](https://community.auth0.com/t/autodesk-sso-on-auth0/199814 "2026-05-11T13:46:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.fung](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/david.fung/32/75193_2.png) [@david.fung](https://community.auth0.com/u/david.fung)\
**Post date:** [May 11, 2026, 1:46pm UTC](https://community.auth0.com/t/autodesk-sso-on-auth0/199814/1 "2026-05-11T13:46:45Z")

</div>

Anyone did the [Autodesk SSO](https://help.autodesk.com/view/SSOGUIDE/ENU/?guid=SSOGUIDE_Okta_Guide_About_Single_Sign_on_SSO_html) connection successfully by Auth0? I don’t know how to do the user attributes mapping. Thanks.

```auto
{
  "audience": "https://www.okta.com/saml2/service-provider/xyz123",
  "mappings": {
    "user_id": "objectGUID",
    "given_name": "firstName",
    "family_name": "lastName",
    "email": "email"
  },
  "passthroughClaimsWithNoMapping": false,
  "mapUnknownClaimsAsIs": false,
  "mapIdentities": false,
  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:2.0:nameid-format:email"
}

```

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [May 11, 2026, 8:06pm UTC](https://community.auth0.com/t/autodesk-sso-on-auth0/199814/3 "2026-05-11T20:06:41Z")

</div>

Hi @david.fung

Welcome back to the Auth0 Community!

Autodesk requires four specific SAML attributes to be present in the SAML assertion: `firstName` , `lastName` , `email` , and `objectGUID`.

To resolve this, you simply need to reverse the keys and values in your mapping block. The keys must be the attribute names Autodesk is expecting, and the values must be the corresponding Auth0 user profile properties.

The JSON payload for your Auth0 SAML configuration should look something like this:

```auto
{
  "audience": "https://www.okta.com/saml2/service-provider/xyz123",
  "mappings": {
    "objectGUID": "user_id",
    "firstName": "given_name",
    "lastName": "family_name",
    "email": "email"
  },
  "passthroughClaimsWithNoMapping": false,
  "mapUnknownClaimsAsIs": false,
  "mapIdentities": false,
  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:2.0:nameid-format:email"
}

```

If you have any other questions, let me know!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![david.fung](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/david.fung/32/75193_2.png) [@david.fung](https://community.auth0.com/u/david.fung)\
**Post date:** [May 12, 2026, 1:33am UTC](https://community.auth0.com/t/autodesk-sso-on-auth0/199814/4 "2026-05-12T01:33:29Z")

</div>

Because “given\_name” and “family\_name” are empty by default, Autodesk rejected it. After I used the Auth0 API to update the two data attributes, it works fine. The below configuration is correct.

```auto
{
  "audience": "https://www.okta.com/saml2/service-provider/xyz123",
  "mappings": {
    "user_id": "objectGUID",
    "given_name": "firstName",
    "family_name": "lastName",
    "email": "email"
  },
  "passthroughClaimsWithNoMapping": false,
  "mapUnknownClaimsAsIs": false,
  "mapIdentities": false,
  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:2.0:nameid-format:email"
}

```

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [May 26, 2026, 1:33am UTC](https://community.auth0.com/t/autodesk-sso-on-auth0/199814/5 "2026-05-26T01:33:50Z")

</div>

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